verified-phase-planning

To generate phase plans and verify dependencies, use a planner-checker workflow that drafts a PLAN.md and validates it against risk and verification gates. This enforces DAG-based task ordering to prevent out-of-sequence work.

A planner-checker loop for phase planning is an iterative cycle that drafts a plan and validates it against dependency and risk gates. It automatically repeats up to 3 cycles to resolve errors and produce a verified PLAN.md.

To prevent circular dependencies during project phase mapping, enforce DAG-based task ordering. This validates dependency order and ensures tasks are sequenced correctly before build execution.

Yes, this phase planning approach integrates risk assessment and gate checks into its validation workflow. The checker validates drafted plans against these gates before allowing phase progression.

Validating phase plans generates a PLAN.md artifact to guide the build and a LEARNINGS.md file. The LEARNINGS.md captures decisions and insights from the planning process for future phase reference.

The main limitation of the planner-checker iteration cycle is a maximum of 3 automated loops. If a PLAN.md cannot pass dependency, risk, and verification gates within 3 cycles, manual intervention is required.