# Phase 2: Review Requirements

Review `docs/ai/requirements/feature-{name}.md` against the `README.md` template.

1. **Search memory** for relevant conventions or past patterns.
2. **Review** each section: problem statement, goals/non-goals, success criteria, user stories, constraints, open questions, template compliance.
3. **Clarify and explore (loop until converged)**:
   - **Ask clarification questions** for every gap, contradiction, or ambiguity. Do not just list issues — actively ask specific questions to resolve them. Example: "Success criteria say 'fast' — what's the target latency?"
   - **Brainstorm and explore options** — For key decisions, trade-offs, or areas with multiple viable approaches, proactively brainstorm alternatives. Present options with pros/cons and trade-offs. Don't just accept the first approach — challenge assumptions and surface creative alternatives.
   - **Repeat** — Clarifying answers may reveal new trade-offs worth exploring, and brainstorming may surface new questions. Continue looping until the user is satisfied with the chosen approach and no open questions remain.
4. **Update** the requirements doc with clarified answers and chosen options.
5. **Store** clarifications in memory.
6. **Summarize** what was validated, what was updated, remaining open items.

**Next**: Phase 3 (Review Design). If fundamental gaps remain unresolvable → back to Phase 1.
