- Read the target
spec/features/<feature-id>-<slug>.mdand project conventions fromAGENTS.md.<feature-id>must useF<epic>.<feature>(example:F1.1).
- Check for:
- Clear problem statement and scope/non-scope
- Acceptance criteria that are testable and unambiguous
- Inputs/outputs defined (formats, schemas, examples)
- Edge cases + error handling expectations
- Test plan is present (unit/integration/e2e as appropriate)
- ADR linkage if decisions are involved
- Produce a short “Spec Gaps” list, then either:
- Propose edits, or
- Apply edits directly if the user asks.
- End by recommending the next skill (usually
write-testsorimplement-feature).
Converted and distributed by TomeVault — claim your Tome and manage your conversions.