When should I use the feature-spec skill?

Use it when you have a feature idea but haven't decided on the technical approach, or when you want to think through the design and requirements before writing any code.

Does this skill write the actual code for the feature?

No, this skill is strictly for the design phase. It produces a specification document. Once the spec is ready, you can use skills like /feature-plan or /auto-implement to start coding.

What is the difference between a 'Spec' and a 'Plan'?

A Spec (produced by this skill) focuses on the 'what and why'—requirements and design. A Plan (produced by feature-plan) focuses on the 'how and when'—the specific implementation steps.

How does the automated review process work?

The skill spawns a 'code-architect' sub-agent that audits your drafted specification against your existing codebase to verify feasibility, consistency, and completeness.

Where does the skill save the specification document?

It follows your project's documentation conventions, typically saving a 'plan-feature-name.md' file in a 'docs' or 'plans' directory, or the project root.

Feature Specification & Design Explorer

Name: Feature Specification & Design Explorer
Author: matthiaskloft

bymatthiaskloft

0•

생산성 및 워크플로

Generates detailed design specifications and architectural requirements for new features through a structured discovery process.

The Feature Spec skill is a specialized tool for Claude Code designed to bridge the gap between a vague idea and a concrete implementation plan. It guides users through an interactive interview to analyze project context, explore architectural trade-offs, and document design decisions before development begins. By applying YAGNI principles and conducting automated architectural reviews, it ensures that every feature is well-reasoned, adheres to project conventions, and is ready for phased implementation or automated deployment.

주요 기능

01Standardized Spec Documentation: Produces professional markdown plan documents with clear requirements and design rationale.

02Automated Design Review: Leverages sub-agents to validate feasibility and identify architectural blockers in the spec.

03Architectural Context Awareness: Analyzes existing code and CLAUDE.md to ensure design alignment with current patterns.

040 GitHub stars

05Interactive Discovery: Conducts a step-by-step interview to define scope, requirements, and success criteria.

06Comparative Trade-off Analysis: Proposes multiple implementation approaches with clear pros, cons, and recommendations.

사용 사례

01Brainstorming the technical approach for complex new functionality before committing to a plan.

02Refining vague feature requests into specific, testable requirements and scoped implementation boundaries.

03Documenting architectural decisions and constraints for team alignment and future reference.

주요 기능

01Standardized Spec Documentation: Produces professional markdown plan documents with clear requirements and design rationale.

02Automated Design Review: Leverages sub-agents to validate feasibility and identify architectural blockers in the spec.

03Architectural Context Awareness: Analyzes existing code and CLAUDE.md to ensure design alignment with current patterns.

040 GitHub stars

05Interactive Discovery: Conducts a step-by-step interview to define scope, requirements, and success criteria.

06Comparative Trade-off Analysis: Proposes multiple implementation approaches with clear pros, cons, and recommendations.

사용 사례

01Brainstorming the technical approach for complex new functionality before committing to a plan.

02Refining vague feature requests into specific, testable requirements and scoped implementation boundaries.

03Documenting architectural decisions and constraints for team alignment and future reference.