dev-flow

Conductor for the canonical dev chain. It does NOT re-implement the sub-skills — each one owns its own logic and its own "when to skip" rules. This skill only picks the tier, orders the stages, and drives them. Match ceremony to stakes: a bug gets three steps, a new subsystem gets ten.

Executor note: this is a prompt, not a script. Sub-skills still pause for user input (grill-me interrogates, pr-craft wants approval). Drive one stage, wait for it to finish, then start the next. Never fire the whole chain blind.

Protocol

Detect tier from the task description (table below). If ambiguous, ask one question: which tier.
Print the plan — the ordered stage list for that tier, each stage marked RUN or SKIP with a one-line reason. Honor each sub-skill's own skip rules (e.g. grill-me skips single-file changes; to-prd skips bug fixes). Reflect those in the SKIP reasons.
Confirm — user says go / edit / abort. Accept partial edits ("skip the PRD", "add adhd"). Record exactly what they approved.
Drive — invoke each RUN stage via the Skill tool, in order. After each returns, checkpoint: report what it produced (file path, decision, diff), then start the next. Stop and surface if a stage can't proceed (fuzzy scope → route back to grill-me; unsettled architecture → route to compass).
Close — after the last stage, one-line summary of artifacts produced (PRD path, ADR path, plan path, PR URL).

Tiers

Detect from the task. When in doubt, pick the lower-ceremony tier and let the user upgrade.