Delivery Planning
An approved design describes what to build; the delivery plan turns it into the work to build it: a dependency-ordered breakdown of epics, stories, and tasks that can go straight into your tracker. It is generated deterministically from the approved design; no AI, so the same design always produces the same plan, and every item traces to the component, flow, control, or gap that caused it.
Plan Availability
Delivery planning is available on the Medium plan and above, on approved packages.
Generate a Plan
On Operate → Delivery, choose Generate. The breakdown derives from the approval baseline:
| Work Item | Where It Comes From |
|---|---|
| Build epics and stories | Each deployable unit or application capability; stories carry requirements as acceptance criteria |
| Deployment stories | Running each unit on its host platform |
| Integration stories | Each data flow, parented to the source component's epic; includes flows into external and legacy systems (the bridge is real work) |
| Foundation and data-store stories | Gateways, identity, secrets, observability, caches, and databases, grouped under synthetic epics |
| Security hardening tasks | Controls failing at approval, scheduled as the final phase |
| Decision spikes | Gaps deferred by exception, so the deferred decision has a home in the plan |
Phases follow the dependency order of the design (foundations first, security hardening last), and every item gets a t-shirt size. Actors and counterparty systems produce no build work; only what your organization builds appears.
One Live Plan, Safe Regeneration
A package has one live plan at a time. Regenerating supersedes a draft silently; superseding an exported plan asks for confirmation and never touches the issues already created in your tracker; they stay where they are, and the new plan starts clean.
Reading the Plan
The panel shows phase → epic → children with type and size chips, per-phase progress bars once the export and sync are running, and totals per capability. On the diagrams canvas, delivery progress appears as per-component badges, so the architecture picture shows what is actually built.
Plans Are for the Funding Conversation Too
The business case embeds the plan's phases, counts, and sizes, which is usually the first place a sponsor asks "how big is this really?"