| name | spec-driven-implementation |
| description | Implement a feature or fix from product/technical specs while checking the final code against the stated requirements. |
Spec-Driven Implementation
Use when the task references a product spec, tech spec, design doc, issue plan, or explicit acceptance criteria.
Workflow
- Read the relevant spec files or acceptance criteria.
- Extract required behavior, non-goals, constraints, and verification gates.
- Map the existing implementation and tests before editing.
- Produce a short implementation plan tied to the spec.
- Make surgical changes only for the requested behavior.
- Check the implementation against each requirement.
- Run the smallest meaningful verification gate and report any skipped gate.
Rules
- Do not implement unstated nice-to-haves.
- If the spec conflicts with existing code or another spec, stop and surface the conflict.
- Preserve public compatibility unless the spec explicitly changes it.
- Add or update tests when behavior changes and the project has relevant tests.
Output
Return:
SUMMARY
SPEC REQUIREMENTS
CHANGES
SPEC CHECK
VERIFICATION
RISKS
