| name | project-specification |
| description | Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning. |
| alwaysApply | false |
| model_preference | claude-sonnet-4-6 |
| category | workflow |
| tags | ["specification","requirements","acceptance-criteria","spec-driven-development"] |
| complexity | intermediate |
| model_hint | standard |
| estimated_tokens | 800 |
| role | library |
Delegation
For detailed specification writing workflows, this skill delegates to spec-kit:spec-writing as the canonical implementation. Use this skill for quick specification needs; use spec-kit for thorough specification documents.
When To Use
- After brainstorming phase completes
- Have project brief but need detailed requirements
- Need testable acceptance criteria for implementation
- Planning validation and testing strategy
- Translating business requirements into technical specs
- Defining scope boundaries and out-of-scope items
When NOT To Use
- Still exploring problem space (use
Skill(attune:project-brainstorming) instead)
- Already have detailed specification (use
Skill(attune:project-planning) instead)
- Refining existing implementation (use code review skills)
- Making strategic decisions (use
Skill(attune:war-room) for complex choices)
Integration
With spec-kit:
- Delegates to
Skill(spec-kit:spec-writing) for methodology
- Uses spec-kit templates and validation
- Enables clarification workflow
Without spec-kit:
- Standalone specification framework
- Requirement templates
- Acceptance criteria patterns
Record the Tradeoff (decision journal)
If the specification settled a design decision with real alternatives (a chosen
data model, an interface boundary, a constraint accepted), record it to
docs/tradeoffs.md before continuing (draft and confirm):
- If leyline is installed, invoke
Skill(leyline:decision-journal) and append
a tradeoff entry (the decision, the options weighed, and what was
sacrificed; set phase to specify). Show the draft; append on
confirmation.
- Fallback (leyline absent): append to
docs/tradeoffs.md using the in-file
ENTRY TEMPLATE; assign the next TR-NNN id.
Post-Completion: Workflow Continuation (REQUIRED)
Automatic Trigger: After Quality Checks pass and docs/specification.md is saved, MUST auto-invoke the next phase.
When continuation is invoked:
- Verify
docs/specification.md exists and is non-empty
