task-pipeline plugin
Runs a substantial task through a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine is built into the skill — no companion plugin required — with typed auto/judgment/manual gates, a frozen requirement spine that closes with evidence, a work board and a verification ledger that outlive a run, an exposure line naming what shipped unconfirmed, a progress rail computed from the project's own config, a proportional short path for small changes, a loop guard whose ceilings stop and record a blocker, and stage-3 tracks for what a product does, how it sounds and how it looks. Two modes need no task: `checkup` (what is unverified) and `setup` (audit existing docs); a third, `waves`, takes the whole board and closes it in waves that each finish in one pass. Retro insights can publish upstream as issues, opt-in and redacted.
How to install the task-pipeline plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add ssheleg/task-pipeline
/plugin install task-pipeline@task-pipelineWhat's inside task-pipeline
19 parts read from the plugin's own files.
Commands 2
Run as /task-pipeline:name- /task-pipeline:project-audit[path] (default: the current project)
Audit a whole project — discover what it is, probe it, read production evidence, and leave an HTML report plus a JSON sidecar. Read-only.
- /task-pipeline:task-pipeline<one-line task> | waves | iteration | setup | checkup
Run a task through task-pipeline's gated stages (intake grill → docs → brainstorm → spec → plan → build → tests → deploy → post-deploy → docs/wiki → acceptance). Also: `waves` — close the whole board in waves; `iteration` — the release loop around the waves; `setup` — audit the docs you already have
Agents 8
Call as @agent-task-pipeline:name- @agent-task-pipeline:agent-testerinherit
The agent-surface review, owed where stage 0's actor branch is armed. Walks the project's agent panel through the agent-channel scenarios of the changed stories, first over the contract source read cold (pass C), then by calling the build through a real client (pass B), judges every step on a fixed
- @agent-task-pipeline:design-testerinherit
The design-review gate, owed by every node that changes an interface. Walks the project's test panel of ten personas through the changed scenarios, first over the Figma frames or mockups (pass D), then in a real browser over the build (pass B), judges every step on a fixed checklist, watches the mac
- @agent-task-pipeline:verifierinherit
Closes one node of the work graph. Reads the diff, the node's REQ and the gate output, and returns a seven-key verdict — what is done with the evidence for each claim, what is not, the blockers and whether the run can continue around them, and a re-plan. Use when a task in a task-pipeline run has fi
- @agent-task-pipeline:verifier-agentinherit
The agent tier of a task-pipeline certification, owed on a public or internal agent surface. Runs the proving call through a real client and the contract tests, compares the served snapshot with the contract source, probes typed errors, scope refusal and idempotent retry, and reads the agent tester'
- @agent-task-pipeline:verifier-productinherit
Tier 3 of a three-tier certification. Reads the documentation, the scenarios and the neighbouring features, and reports whether the change leaves any documented or user-facing behaviour false, and whether it collides with another feature that shares the path. Returns an eight-key tier report. Use as
- @agent-task-pipeline:verifier-seaminherit
Tier 2 of a three-tier certification. Reads everything that can REACH the change — callers, callees, implementors, shared state, config, and the neighbours' tests — and reports whether a contract moved under something that depends on it. Returns an eight-key tier report. Use as one of three blind re
- @agent-task-pipeline:verifier-unitinherit
Tier 1 of a three-tier certification. Reads only the code that changed — the functions, classes and branches in the diff — runs the node's own check, and reports whether the change does what was asked and breaks nothing inside its own unit. Returns an eight-key tier report. Use as one of three blind
- @agent-task-pipeline:verifier-visualinherit
Tier 4 of a task-pipeline certification, owed on a flagship or product surface. Reads the contact sheet, the director record, the project linter's output and the rubric, and reports whether what a user SEES carries the intent the record set — every state in the matrix, no gate item failing under a p
Skills 3
Claude loads it when the task matches- evidence-docs
Use when writing or reviewing anything read as true: a decision record, ADR, README, acceptance report, runbook, changelog, audit finding, a claim of verification. Applies the ten canons of evidence-backed docs. Not for: drafts, chat answers, commit messages; 'без доков' opts out.
- project-audit
Use when someone asks what is true of a whole project ('project audit', 'аудит проекта'): finished, broken, unexplored. Probes it, reads production evidence, leaves a JSON sidecar. Read-only. Not for: one deliverable in a run, a diff review, a skill's construction; 'без диагностики' opts out.
- task-pipeline
Use when work changes the repository: feature, fix, refactor, migration, integration, audit fixes; фича, баг, интеграция, фикс по аудиту. Runs a substantial task via gated stages to acceptance; 'waves'/'волнами' closes the board. Not for questions or one-line edits; 'без пайплайна' opts out.
Hooks 6
Runs on these events- PostToolUsecommand
Bash, Bash|Edit|Write|MultiEdit|apply_patch
- PostToolUseFailurecommand
Bash
- PreCompactcommand
No description in the file.
- PreToolUsecommand
Bash, Edit|Write|MultiEdit|NotebookEdit|apply_patch
- SessionEndcommand
No description in the file.
- SubagentStopcommand
No description in the file.
Using task-pipeline in Claude Code
Type a command in a Claude Code session:
/task-pipeline:project-audit [path] (default: the current project)
/task-pipeline:task-pipeline <one-line task> | waves | iteration | setup | checkupAsk for an agent by name:
@agent-task-pipeline:agent-tester
@agent-task-pipeline:design-testerSkills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update task-pipeline@task-pipeline
- Refresh the marketplace
- /plugin marketplace update task-pipeline
- Turn it off for now
- /plugin disable task-pipeline@task-pipeline
- Remove it
- /plugin uninstall task-pipeline@task-pipeline
Skills in task-pipeline
- evidence-docsssheleg/task-pipeline
Use when writing or reviewing anything read as true: a decision record, ADR, README, acceptance report, runbook, changelog, audit finding, a claim of verification. Applies the ten canons of evidence-backed docs. Not for: drafts, chat answers, commit messages; 'без доков' opts out.
8 files7stars - project-auditssheleg/task-pipeline
Use when someone asks what is true of a whole project ('project audit', 'аудит проекта'): finished, broken, unexplored. Probes it, reads production evidence, leaves a JSON sidecar. Read-only. Not for: one deliverable in a run, a diff review, a skill's construction; 'без диагностики' opts out.
4 files7stars - task-pipelinessheleg/task-pipeline
Use when work changes the repository: feature, fix, refactor, migration, integration, audit fixes; фича, баг, интеграция, фикс по аудиту. Runs a substantial task via gated stages to acceptance; 'waves'/'волнами' closes the board. Not for questions or one-line edits; 'без пайплайна' opts out.
87 files7stars
task-pipeline plugin questions
How do I install the task-pipeline plugin?
In Claude Code run /plugin marketplace add ssheleg/task-pipeline, then /plugin install task-pipeline@task-pipeline.
What does the task-pipeline plugin include?
task-pipeline bundles 2 commands, 8 agents, 3 skills, hooks.
What commands does the task-pipeline plugin add?
It adds /task-pipeline:project-audit, /task-pipeline:task-pipeline. Run them in Claude Code with the plugin prefix, for example /task-pipeline:project-audit.
Which agents come with task-pipeline?
agent-tester, design-tester, verifier, verifier-agent, verifier-product, verifier-seam +2. Call one with @agent-task-pipeline:agent-tester.
How do I update or remove the task-pipeline plugin?
Update it with claude plugin update task-pipeline@task-pipeline in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall task-pipeline@task-pipeline.
What license is the task-pipeline plugin under?
MIT, as stated in the plugin's manifest.