task-pipeline CLAUDE.md

CLAUDE.md

Guidance for Claude Code when editing this repository. User-facing documentation lives in README.md; the full artifact contract lives in docs/contract.md.

Quick orient

A collection of user-invocable Claude Code skills implementing a chat-first "context serialization protocol", not an orchestration engine: discuss freely in chat, then fix the discussion into a fixed-format Markdown artifact under .task/ with one short skill. Depth of capture is the skill name, never a flag. Skills in skills/<name>/SKILL.md; the plugin ships exactly one agent, agents/code-reviewer.md (the review pass — see the invariants below), and no phase companions, no lock protocol, no hook gate. No build/test/lint. Work here is editing markdown (occasional bash) and reasoning about pipeline semantics.

discuss freely in chat
  ↓
grill                                 ← pre-capture: interrogate the decision, no artifact
  ↓
to-task | to-plan | to-roadmap        ← capture depth is the skill, not a flag
to-spec                               ← pins technical decisions, cited via Spec:
  ↓                       ↓
implement session   roadmap-to-workflow   ← the launcher fans items out to sessions
  ↓                       ↓
task:code-reviewer                    ← the plugin's own review pass, spawned by both:
                                        prove → fix within Touches → Build and Tests → amend

grill sits at the "discuss freely" stage: it interrogates a plan/decision one question at a time, keeps a decision-plus-rationale ledger, ends with a pre-mortem, and routes to the right capture skill — it writes no artifacts and touches nothing under .task/. to-task captures ## Description only into .task/task/<slug>.md; to-plan adds ## Plan (Goal/Touches/Logic steps); to-roadmap captures a multi-task initiative into .task/roadmap/<slug>.md; to-spec captures load-bearing technical decisions into a standalone .task/spec/<slug>.md, referenced by tasks/roadmaps via a Spec: header and read by the executing session as a fixed anchor. There is no execution skill — every artifact carries a stamped one-line ## Execution pointer to .task/CLAUDE.md → ## Executing a task, and an ordinary session told implement .task/task/<slug>.md follows it: implement the plan, commit per .task/CLAUDE.md → Commit Format, spawn task:code-reviewer on the resulting diff (it proves each finding, fixes what it confirms within Touches, runs .task/CLAUDE.md → Build and Tests, and amends the commit), tick the roadmap item if Roadmap:/Source item: are present. roadmap-to-workflow is the one launcher: it computes dependency-ordered waves over a roadmap's unchecked items and invokes the plugin-shipped Workflow driver (skills/_lib/roadmap-driver.js, via scriptPath + args) — opus-plans (sonnet for haiku-hinted items)/sonnet-implements/task:code-reviewer-reviews per item by default, plus the driver's own mark stage ticking the checkbox.