Section 4 · Clarification Gate
Removing Ambiguity
Resolve every open item in requirements.md. Document each decision — lock in clarity before tasks or code.
Ready for Plan Checklist
Before advancing to /create-tasks, confirm every item passes. If any fails, return to shape-spec.

- No [NEEDS CLARIFICATION] items remain
- Success criteria are measurable
- Roles and permissions are explicit
- Error behavior is explicit
- Data lifecycle is explicit
- DO NOT constraints are present
Clarification Gate
Zero unresolved items in requirements.md before implementation. Toggle items below to see the gate in action.
Gate closed — resolve open items first
2 open items remaining
Platform format: documentation-only repo, or evolve into a web app (React + Supabase)?
→ Evolved into this Next.js showcase app — docs + interactive learning UI.
PRD vs sections: formal PRD per section, or section README sufficient?
shape-spec workflow: specific CLI/tool, or manual conversation checklist?
Each resolved item should include: question, resolution, date, and who decided. Ambiguity carried forward multiplies errors in tasks and implementation.