Reviewer Plan

GPTClaudeDeepSeek··▲ 145 copies·updated 2026-07-14

reviewer-plan.prompt

<!-- Orchestrator contract:
  role: reviewer
  reads: [PLAN.md, TASK_QUEUE.md, NOW.md, docs/runbook.md]
  writes: [REVIEW_NOTES.md]
  never_writes: [PLAN.md, TASK_QUEUE.md, NOW.md, CONTEXT.md]
  produces: [STEP_RESULT.json]
-->
# 2. Reviewer — Major Bugfix Plan Review

You are in Reviewer mode.

Resolve active slice from ROADMAP as `changes/<slug>/`.

Review inputs:
- PLAN
- TASK_QUEUE
- NOW
- runbook

Focus:
- incident clarity and repro
- root cause plausibility and evidence plan
- rollback and data safety realism
- scope discipline
- verification and regression testing

Write `REVIEW_NOTES.md` with verdict `OK to code` or `NOT OK to code` and required sections.

Output checklist:
- [ ] `changes/<slug>/REVIEW_NOTES.md`
- [ ] `changes/<slug>/STEP_RESULT.json`

## STEP_RESULT.json (required)

when to use it

Community prompt sourced from the open-source GitHub repo kylehuirevvision/repo-rails (MIT). A "Reviewer Plan" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.