delivery-high-level-plan

To turn validated user stories into an execution plan, use a planning sub-agent to generate a high-level plan with objectives, steps, dependencies, and risk flags. This process enforces a mandatory delivery sequence and prevents conflicts using an anti-collision guard.

An anti-collision guard works during plan generation by enforcing a mandatory delivery sequence. This prevents execution conflicts when transforming validated stories into a high-level plan, ensuring dependencies and steps are ordered safely for governance-driven delivery.

You need high-level planning for simple stories when you require a sole, compact execution plan to guide delivery. Generating a high-level plan provides governance by defining objectives, steps, and dependencies through the Planning Sub-Agent workflow.

Yes, you can generate a plan document for simple stories as the sole plan. The planning sub-agent produces this high-level execution plan at contexts/artefacts/plans/{id}.plan.md, complete with objective, steps, dependencies, and risk flags.

Tier 1 micro-delivery planning breaks work into the smallest executable units, while Tier 2 and Tier 3 planning passes refine those units further. Both are supported when generating a high-level plan, ensuring governance scales from simple stories to complex dependencies.