#29 Critical: doer-reviewer flow says PM reviews instead of dispatching reviewer

[Anonymous]

Originally created by: kumaakh

Bug (Critical)

The execution loop in doer-reviewer.md and SKILL.md says:

member hits verify checkpoint → STOPS → PM reads progress.json
  → PM reviews → resumes member → repeat

This is wrong. "PM reviews" implies the PM itself reviews the code and resumes. The correct flow is:

member hits verify checkpoint → STOPS → PM reads progress.json
  → PM dispatches REVIEWER to review → reviewer commits verdict
  → APPROVED → PM resumes doer → repeat
  → CHANGES NEEDED → PM sends feedback to doer → doer fixes → repeat

Impact

The PM skips the reviewer entirely at every VERIFY checkpoint and auto-resumes the doer. This defeats the entire purpose of the doer-reviewer pair. In Sprint 7, 4 phases of code went through without a single reviewer check — the reviewer was only used for plan review and final review.

Fix

Update the execution loop in both doer-reviewer.md and SKILL.md to explicitly state that the PM must dispatch the reviewer at every VERIFY checkpoint, not review itself.

[Anonymous]

Originally posted by: kumaakh

Fixed in PR [#30]

[Anonymous]

Ticket changed by: kumaakh

• status: open --> closed