plan-review

Plan validation involves reviewing a workflow plan artifact for architecture simplicity, sequencing, and build readiness before proceeding to implementation. Two substantive reviewers plus one skeptic assess the plan to produce a go/no-go decision.

A findings-first plan review artifact is a concise markdown document written to a repository's docs folder. It captures review decisions and links to prior rounds, ensuring later implementation stages can proceed without relying on chat history.

Reviewing a plan.md file for buildability requires deriving the workflow slug from the dossier and validating full-stack coverage, restartability, and test readiness. The review outputs a zero-padded round artifact to the reviews directory with a clear advance or revise recommendation.

Plan review requires exactly two substantive reviewers plus one skeptic to validate readiness. It must verify reviewer role bindings to ensure proper architecture, engineering, and adversarial realism coverage before generating a recommendation to advance or revise.

You should not use automated workflow plan review when a plan.md artifact does not exist in the docs/workflows directory. The review process depends on reading this specific file and deriving a slug from the dossier to function correctly.