pipelinelisted

# Superb Pipeline ## Purpose Pipeline is a thin controller around Superpowers. It keeps the approved design, plans, decisions, execution state, and evidence in project files so a compacted or restarted session can continue without inventing requirements or repeating work. The controller owns orchestration and durable transitions. It does not reimplement the skills that investigate, plan, implement, debug, review, and verify the work. ## Invocation Trim whitespace from this complete argument string, then select exactly one mode: `$ARGUMENTS` | Argument | Mode | | --- | --- | | empty | Full run: begin with planning. | | `resume` | Resume one compatible v2 run from its files and Git evidence. Never create or replace a run. | | `status` | Strictly read-only inspection. Do not lock, write, reconcile, dispatch, test, fix, or initialize. | | anything else | Stop and ask what the user meant. Do not guess a verb or expose an internal remediation mode. | Use the whole argument string, never an indexed positional placeholder. For `resume` or `status`, use [references/persistence.md](references/persistence.md). If no run is identifiable, report that. If multiple runs qualify, ask the user which one. Recency is not selection authority. ## Zero-assumption law Before making any required decision, inspect these sources in order: 1. the user's explicit instructions; 2. recorded explicit user answers; 3. the approved design/specification; 4. the approved master plan and phase plans