This skill should be used when the user mentions "continue spec", "work on spec", "check requirements", "update progress", "spec 001", or wants to work with an existing specification directory. Provides guidance for reading, navigating, and updating spec files during implementation.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides guidance for working with existing specification directories during implementation.
Spec directories contain structured documentation for features under development:
requirements.md - Problem statement and success criteria (EARS notation)design.md - Architectural approach and key decisionstasks.md - Implementation plan and progress trackingnotes.md - Implementation details and learningsThis skill activates when:
List the specs/ directory to find existing specs:
specs/
├── backlog.md # Future spec ideas
├── 001-feature-name/
├── 002-another-feature/
└── 003-third-feature/
Specs are numbered sequentially (001, 002, etc.). When user says "spec 3" or "spec 003", look for specs/003-*/.
Read all files in the relevant spec directory to understand:
requirements.md for success criteria - implementation must satisfy thesedesign.md for architectural decisions to followtasks.md for current progress and next stepsdesign.mdtasks.md as they finishnotes.mdnotes.md under Learnings sectiondesign.md if architectural decisions changerequirements.md if scope changes (confirm with user first)Two sections to maintain:
Plan - Strategic approach (update if approach changes)
Progress - Checklist of tasks
- [x] Task descriptionImplementation Details - Technical decisions, code patterns used
Learnings - Insights discovered during implementation, gotchas for future reference
Only update with user confirmation. Changes here affect scope.
Update when:
Infer spec status from tasks.md:
When one spec relates to another, note the relationship in design.md or notes.md:
Related: See [spec 002](../002-related-feature/) for the authentication approach.
${CLAUDE_PLUGIN_ROOT}/shared/references/spec-driven-development.md - Philosophy and conventions of this approach${CLAUDE_PLUGIN_ROOT}/shared/references/ears-notation.md - EARS syntax for writing unambiguous requirements