SpaiR/task-pipeline
7 stars · Last commit 2026-08-02
Interrogate the plan, capture what survived, implement it in any session — a chat-first task plugin for Claude Code.
README preview
# task-pipeline [](https://github.com/SpaiR/task-pipeline/releases) [](LICENSE)  **Docs & guides → [spair.github.io/task-pipeline](https://spair.github.io/task-pipeline/)** > A plan file is only as good as the argument that produced it. ```text You: "Let's cache the API responses in Redis." Claude: "Great idea! I'll start implementing." ``` That second line is where projects quietly go wrong: the model agrees and starts building before the plan was ever argued. `task-pipeline` keeps the discussion and the doing apart, and sizes the paperwork to the task. Talk it through in chat; when you're ready, one command freezes that discussion into a single Markdown file under `.task/` at the depth you pick — `to-task` for the what and why, `to-plan` to add a stepwise plan, `to-roadmap` for a multi-task initiative, `to-spec` to pin the load-bearing decisions. Then any session — this one, or a fresh one tomorrow — implements that file the same way: work the plan, commit, then hand the diff to the plugin's own reviewer agent, which proves each finding before it touches anything, runs your build and tests, and folds its fixes into that commit. And when "talk it through" needs teeth, `/task:grill` interrogates the plan first (optional): one question at a time, its recommendations allowed to disagree with you, closing on a pre-mortem — so what gets frozen is what survived the questioning, not the first idea that sounded good. It's for tasks longer than one session; a two-file, twenty-minute fix doesn't need any of this, and leaves no trace either way — [here's exactly what it will and won't touch](#why-you-can-trust-this). ```text