Feature Spec

Step 2 after feature-plan. The plan answers what and why; the spec answers how. Output is for engineers who will implement.

Workflow

1. Require the plan. Ask for the path to the PLAN.md (or read it from docs/plans/). The spec must link back to it via the Related Plan field. If no plan exists, run feature-plan first — don't synthesise a spec without an agreed plan.

2. Gather technical inputs:

   • Folder structure convention (default: src/modules/<module-name>/).
   • Stack hints (ORM, framework, DB) — read from package.json / repo if unstated.
   • For each major component in the plan: file responsibilities, endpoints, auth model, edge cases.
   • Existing data models that interact with the new ones.
   • Test stack (Jest, Vitest, Supertest, etc.) — sniff from package.json.