Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Feature specification creation from codebase research. Produces requirements, acceptance criteria, architecture decisions, implementation plans, and risk analysis.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | -36% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -11% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 10% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 7% | 0% |
| case-18 | ✗→✓ | ▲ Improved | -36% | 0% |
Clear boundaries on what the feature does and does not include.
Detailed requirements with unique identifiers for tracking.
Testable, measurable criteria for each requirement.
Decision records with rationale and alternatives considered.
Phased approach ordered by dependency, not priority.
Identified risks with probability, impact, and mitigation strategies.
Interface definitions and data model schemas.
Mapping of unit, integration, and E2E tests to requirements.
Specifications are saved to docs/specs/{feature}.md for reference by the execution workflow.
/spec:create [feature] slash commandclaudekit-spec-workflow (create mode)Other measured skills in the registry, with their headline benchmark lift.