Back to skills
Specification
Specs
/hapo:specs
Creates the durable feature contract: requirements, research, design, task packets, and validation state.
Use When
- The direction is clear enough to become requirements.
- You need task files before coding.
- The feature needs traceable scope and evidence gates.
Flow
01 / Detect
Check incomplete specs and avoid duplicates.
02 / Requirements
Write behavior, constraints, and acceptance criteria.
03 / Research
Record source-backed findings and decisions.
04 / Design
Define architecture, contracts, data flow, and invariants.
05 / Tasks
Split work into task packets with evidence criteria.
06 / Validate
Check spec.json, task files, and registry alignment.
Output
A `specs/<feature>/` directory ready for task-by-task implementation.
Avoid
Do not use specs as decoration after code is already guessed. The spec should constrain implementation.
Next Handoff
/hapo:develop