Dev Phase Reviewer

Phase Reviewer

Mandatory review gate for every /dev phase.

Core rules

1. Reviewer must differ from the author.
2. Review must be strict and independent.
3. Any deliverable change after review requires re-review.
4. Review results must be persisted to docs/reviews/phase-{NN}-{phase_key}.md.
5. Reviewer must read mapped textbook references before reviewing.
6. Reviewer must verify textbook compliance and update docs/process/textbook-compliance-log.md if the process was violated.

Reviewer assignment

Phase to checklist mapping

Workflow

1. Read the current phase from .dev-state.yaml.
2. Determine the reviewer from the table above.
3. Determine the review type and checklist.
4. Read .agent/config/textbook-skill-mapping.yaml.
5. Resolve relevant topics with textbooks/topic_index.json.
6. Read the relevant textbook excerpts under data/mineru_output/.
7. Run automatic validation for the phase.
8. Execute the checklist, including textbook-compliance checks.
9. If textbook lookup was skipped or backfilled late, append an entry to docs/process/textbook-compliance-log.md.
10. Generate or update docs/reviews/phase-{NN}-{phase_key}.md.
11. If any CRITICAL or HIGH finding exists, block the phase and require re-review after fixes.
12. Update .dev-state.yaml only after the review gate passes.

Automatic validation

Output requirements

Review reports must include:

• automated validation results
• findings ordered by severity
• textbook basis summary
• final conclusion
• re-review section if fixes were made after initial review