delivery-planning

name	delivery-planning
description	Use after an approach is approved to create an implementation plan with bounded tasks, dependencies, exact outputs and verification. Prefer Superpowers writing-plans or GitHub Spec Kit when installed and appropriate.

Delivery Planning

1. Read the approved design, specification and current repository.
2. Decompose work into bounded tasks with:
   • outcome;
   • exact files or artifact;
   • dependencies;
   • acceptance;
   • verification;
   • owner or agent type.
3. Identify tasks safe for parallel execution.
4. Identify shared-state tasks that must remain sequential.
5. Define checkpoints, rollback and merge order.
6. Assign phase-specific skills and agents rather than one global stack.
7. Keep the plan implementation-oriented.

A task is not ready when its output or verification is ambiguous.