kanbanzai-plan-review

Automating an auditable plan review requires validating scope, feature completion, spec conformance, and documentation currency. You provide a Plan ID, plan documents, feature statuses, and decision logs to verify terminal feature states and surface blocking findings before approval.

Plan scope verification maps project goals to delivered features and flags any scope additions or removals that lack documented decisions in the decision log, ensuring full traceability before plan approval.

Feature completion checks verify that every feature reaches a terminal state—done, cancelled, or superseded—before plan approval. Cancelled or superseded features require documented rationales to pass the review workflow.

Spec conformance validation confirms that done features have approved specifications and ensures no draft specifications exist for released work, guaranteeing that completed features meet documented requirements.

Running an automated plan review requires a Plan ID, plan documents, current feature statuses, and decision logs to perform verification, capture open issues, and generate retrospective synthesis with governance actions.

When blocking findings are surfaced, the plan remains unapproved until issues are resolved. The workflow captures open issues, deferrals, and decision gaps to ensure traceability before transitioning the plan state upon approval.