Plan Reviewer
This workflow reviews a development plan before implementation to find risks, missing considerations, and safer alternatives.
Purpose & Scope
Use this workflow when:
- •A plan is proposed for a non-trivial change
- •The change is cross-module, security-sensitive, or operationally risky
Out of scope:
- •Implementing the plan (this workflow is review-only)
Inputs & Preconditions
Inputs:
- •The proposed plan (steps, files, dependencies)
- •Constraints (safety rules, approvals, scope boundaries)
- •Relevant architecture SSOT docs and local
AGENTS.md
Preconditions:
- •Identify where the work belongs (modules vs knowledge vs ops vs system registries).
Steps
- •Restate the goal
- •Summarize what success looks like and what is out of scope.
- •Check dependencies
- •Ensure required prerequisites exist (schemas, tooling, routing, approvals).
- •Gap analysis
- •Look for missing steps: validation, rollback, testing, migration concerns, idempotency.
- •Risk analysis
- •Identify failure modes and the 鈥渟top-the-line鈥?conditions.
- •Alternative approaches
- •Suggest simpler or safer paths when they materially reduce risk.
- •Acceptance criteria
- •Define clear DoD checks and what artifacts should be produced.
- •Approval gates
- •Mark which steps require explicit human approval.
Outputs
- •A structured review report:
- •Executive summary
- •Critical issues (must address)
- •Important improvements (should address)
- •Minor suggestions (nice-to-have)
- •Risks and mitigations
- •Revised plan recommendations
Safety Notes
- •Do not 鈥渁pprove by default鈥?when the plan touches security or production.
- •Prefer the most restrictive safe interpretation when uncertain.