task-pipelinelisted

# task-pipeline Self-contained orchestrator. Runs a task through **gated stages**, each carrying its own built-in doctrine — no companion plugin required. Keeps the main thread disciplined: no stage advances until its gate passes; the whole run uses one model, confirmed before it starts. **Grill first, then run autonomously.** A one-line task ("make me feature X") is never enough to finish without a human in the loop. Stage 0 is **mandatory**: a relentless, one-question-at-a-time interview that resolves every decision branch *and* sweeps stages 1→10 for anything that would stop the run later — then locks the answers into a brief. Autonomy is bought there or not at all; every question skipped at stage 0 comes back as an interruption at stage 6. **Config contract: [`pipeline.schema.json`](pipeline.schema.json).** A pipeline is a machine-readable config — an ordered list of stages, each with `skills[]` (the skills/agents that run it) and a `gate {type, check}`. The schema is the universal contract; it imposes **no** specific stages, skills, or gate assignments. [`pipeline.example.json`](pipeline.example.json) is a **copy-and-rewrite example** that encodes this plugin's own default flow (stage 0 intake + the 1→10 stages tabled below) and an optional, toggleable `release` block. Any project replaces it wholesale — any number of stages, run by its own skills/agents, with its own gate types (see *Bring your own skills*). Each gate has a **type**: `auto` (the orchestrator verifies