| name | spec-management |
| description | Manages spec files for requirements capture and validation |
Spec Management Skill
When Claude Activates This Skill
This skill activates when:
- User requests a new feature or implementation
- User asks to modify existing functionality
- A task requires planning before implementation
- Validation against requirements is needed
What This Skill Enables
1. Requirements Capture
- Extract requirements from user prompts
- Create minimal, focused spec files
- Avoid scope creep and assumptions
2. Spec File Management
- Create specs in
docs/specs/
- Move existing specs to
docs/specs/draft/ before updates
- Maintain spec version history
3. Implementation Validation
- Verify changes against spec requirements
- Ensure acceptance criteria are met
- Track completion status
How Claude Uses This Skill
New Feature Request
- Use Explore agent to understand codebase
- Use Plan agent to design approach
- Create spec file with user's requirements only
- Commit spec before implementation
- Implement feature
- Validate against spec
- Add unit tests
Updating Existing Feature
- Move existing spec to
docs/specs/draft/
- Create updated spec with new requirements
- Commit spec changes
- Implement changes
- Validate against updated spec
Spec File Format
# Feature Name
## Requirements
- [User's direct requirements]
## Acceptance Criteria
- [Testable conditions]
## Notes
- [Clarifications only]
Best Practices
- Keep specs minimal: Only what user requested
- Commit specs first: Before any implementation
- Validate continuously: Check spec during development
- Test coverage: Unit tests for acceptance criteria
- Don't wait for CI: Push and continue, check later
Requirements
docs/specs/ directory exists
docs/specs/draft/ directory for archived specs
- Git for version control
Limitations
- Specs only capture explicit requirements
- Does not auto-generate tests
- Requires manual validation