software-delivery
Route executable implementation planning and multi-part engineering coordination after intent is sufficiently approved; not for architecture selection or release approval.
SKILL.mdSKILLS/software-delivery/SKILL.md
GitHubSoftware Delivery
Choose one primary mode and read only its workflow. Load both only when a durable plan and active cross-boundary coordination are both requested.
| Mode | Use when | Workflow |
|---|---|---|
implementation-planning |
Produce phases, write sets, dependencies, validation gates, rollout, and handoffs. | Implementation planning |
engineering-execution |
Coordinate ownership, sequencing, integration risk, conflicts, and readiness during execution. | Engineering execution |
Do not load sibling workflows or artifacts prospectively. Preserve user-owned changes and stop when requirements, authority, ownership, or validation paths are unresolved.