Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Write feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 24% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -10% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -19% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 3% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -58% | 0% |
Specifications describe desired behavior from the user's perspective. They define what the system should do, not how it should be built. Business value must be explicit in every requirement.
Invoke via babysitter process: methodologies/spec-kit/spec-kit-specification Full pipeline: methodologies/spec-kit/spec-kit-orchestrator
Other measured skills in the registry, with their headline benchmark lift.