What problem does it solve? Running an entire design-to-PR delivery flow in one growing conversation is expensive and fragile: context is re-read every turn, and work cannot resume after an interruption. This Skill splits the flow into isolated phase subagents that hand work over through files, keeping the orchestrator context small and each phase restartable. ## Core Features & Use Cases - Phase isolation with file hand-over: Each phase (cr, plan, implement, review, verify) runs as a fresh subagent that reads entry artifacts, invokes a child skill, writes an exit artifact, and returns only a short status. - Per-phase model routing: Mechanical work like CI polling runs on cheap models while load-bearing judgement like the final whole-branch review runs on the most capable model, with escalation rules recorded in the ledger. - Resumable flow ledger: A git-ignored ledger at .superpowers/flow/<slug>.md tracks phase completion, rulings, and model escalations so the flow resumes from the first unchecked phase after any interruption. - Use Case: A developer with a settled ADR asks to run the dev flow; the orchestrator files the CR via design-to-cr, generates a plan, drives subagent-driven implementation, runs code review, polls CI, and gates each phase for human approval. ## Quick Start Ask the assistant to run the dev flow for your settled design, naming the ADR path and doc PR so it can create the ledger and dispatch the cr phase.
