/the-flow — SDD pipeline dispatch

One public skill for the whole SDD pipeline, built to the flow-architecture pattern (docs/skills-pipeline/flow-architecture.md): the sub-skills (contract-bound verbs, one per stage) live in references/stages/, the guided-mode engine in references/00-routing.md, the coaching voice in references/coach.md. New to the flow? references/getting-started.md.

Progressive disclosure is the contract: load exactly one sub-skill for the current step — never read all of them up front.

Two load paths

Guided — /the-flow (no args, or <slug> / <ord>-<slug>):

1. Read references/00-routing.md (entry paths, state contract, the Graph) and references/coach.md (rail, narration, print-then-offer).
2. Resolve fresh / resume / adopt per 00-routing.md; load only the current stage's sub-skill when a step is accepted, and coach the seam.
3. Guided mode owns all the-flow state writes: it writes .the-flow-state.json directly, and drives the flight plan (the-flow.json → the-flow.md) only through harness flow calls (plan 024 — the CLI is the generator; run the capability precheck first, § Prerequisite). Before the first flight-plan mutation of a session, also load references/flight-plan-ops.md — the nav model, the spine-vs-excursion rule, and the verb flags + gotchas (loaded on demand, not up front; sub-skills never load it).

Direct jump — /the-flow <id> <verb> [flags]:

1. Resolve the stage via the Registry below. Id and verb each resolve alone (typing 6 ≡ typing implement); when both are given they must name the same stage — if they disagree, show the Registry and ask which was meant (never guess).
2. Read only that sub-skill and follow it with the given flags (same flags the verb has always taken).
3. No coach, no rail, no state writes — and no harness seams (harness orchestration is the guided engine's job — direct-jump runs the bare verb, harness-less by design). Artifacts land where they always did; the next guided run discovers them by existence and catches state up.