delivery-flow

Delivery Flow Orchestrator

Design Principle

This skill is the ORCHESTRATOR. It coordinates the delivery team through a structured pipeline but NEVER produces domain artifacts directly. All domain work — requirements, designs, architecture, code, tests, plans — is delegated to worker skills operating as sub-agents with isolated context. Full doctrine elaboration, Core Principles 1–7, Anti-Patterns catalogue, and Guardrails detail: see delivery-team/references/shared/orchestrator-doctrine.md.

Model awareness (Opus 4.7 / F-08): Under F-08, the 4.7 runtime dispatches fewer sub-agents by default unless explicitly steered. "One Role = One Sub-Agent" (Phase 4) is a behaviourally load-bearing gate, not a style preference. Role-count under-dispatch is the highest-confidence regression mode on 4.7.

---

Phase 0: Setup Wizard

Before the pipeline executes, check for project configuration:

State Detection (Resume Check)

Before checking config, check for an existing pipeline state:

1. Check for .delivery/state.md in the current working directory.
2. If state exists with status: in_progress:
   • Read the YAML frontmatter to load pipeline state.
   • Announce: > Existing pipeline found: [pipeline_id], started [date], last completed Stage [N] ([name]). Currently at Stage [N+1].
   • Validate: verify all artifact files in the artifacts map exist on disk. If any are missing, announce which and offer: Restart from that stage / Abandon.
   • Semantic validation: current_stage in range 1-7, not in stages_completed, no gaps in completed+skipped.
   • Config divergence check: diff config_snapshot against current .delivery/config.yml. If different, warn: "Config has changed since this pipeline started. Resume uses the original config. Choose Restart to apply new config."
   • Offer the user: Resume / Restart / Abandon
   • Resume: load config from snapshot, skip completed stages, start at current_stage.
   • Restart: move state file to .delivery/state-archive/state-<timestamp>.md (cap at 5, delete oldest), start fresh.
   • Abandon: delete state file, no pipeline runs.
3. If state exists with status: aborted:
   • Announce: > Aborted pipeline found from [date], stopped at Stage [N]. Artifacts from stages [list] are preserved.
   • Offer: Resume / Restart / Abandon (same as above).
4. If state exists with status: completed: ignore (previous run finished normally).
5. If no state file exists: proceed to config check (normal flow).