spec-feature
Structure feature specs to survive a clean-room build session.
Install
mkdir -p .claude/skills/spec-feature && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16992" && unzip -o skill.zip -d .claude/skills/spec-feature && rm skill.zipInstalls to .claude/skills/spec-feature
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Deeply spec ONE feature before building it — a single attended session that interviews the feature (every screen, state, interaction, edge), composes its screens from the already-decided design system's real workbench components, and authors its milestones with logic + UX-completeness + fidelity done-conditions.Key capabilities
- →Interview a feature to define every screen and surface it touches
- →Define every state per surface, including empty, loading, error, and happy path
- →Specify every interaction required for the feature, such as sort, filter, and drag
- →Detail the exact data each surface shows, pulled from the data model
- →Resolve edge cases like permissions, validation, and conflicts
- →Conduct scoped reference research for interaction patterns from comparable products
How it works
This skill deeply specs one feature by interviewing it to define screens, states, interactions, and data, composing screens from design system components, and authoring milestones with logic and UX-completeness. It includes scoped reference research for interaction patterns.
Inputs & outputs
When to use spec-feature
- →Specifying new features
- →Authoring milestones
- →Defining user interactions
About spec-feature
Provides a rigorous process for scoping features, ensuring every edge case and state is defined before building to ensure the final implementation matches the spec.
Deeply spec ONE feature before building it — a single attended session that interviews the feature (every screen, state, interaction, edge), composes its screens from the already-decided design system's real workbench components, and authors its milestones with logic + UX-completeness + fidelity don
When not to use it
- →When building a brand-new, multi-feature greenfield app (run kickoff sequence first)
- →When exploring a design direction (use `app-design-directions` instead)
- →When the app-level skeleton is being defined (use `spec-foundation` instead)
Prerequisites
Limitations
- →Intended for one feature at a time
- →Requires existing kickoff outputs like product backlog and architecture
- →Assumes a built component gallery from the design system
How it compares
This skill provides a rigorous, single-feature-focused specification process that ensures every detail is defined before building, contrasting with a generic approach that might leave many aspects to be decided during implementation.
Compared to similar skills
spec-feature side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| spec-feature (this skill) | 0 | 3mo | No flags | Advanced |
| project-planner | 32 | 11mo | Review | Intermediate |
| spec-kit-workflow | 11 | 10mo | No flags | Intermediate |
| specification-architect | 13 | 10mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
architecture
davila7
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
context-driven-development
wshobson
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and workflow.md files.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context