Every piece of work — idea, plan, backlog, bug — boards its own line, and every line converges on the same spine: implement → wrapup → retro. implement drives tdd internally — red → green → refactor at pre-agreed seams, code-review before landing.
routersize unclear? start here
scale-check
3–6 questions→
Program → program line/
Feature → main line/
Direct-Slice → implement/
Bug → repair line
main lineidea → shipped
idea / plan / issue→
grill? — see grill line→
to-prd→
to-issues→
gate→
implement
drives tdd inside→
wrapup→
retro
grill lineas deep as the stakes
mechanical change → none/
grill-me
relentless interview, one question at a time/
grill-with-docs
+ CONTEXT.md, ADRs updated inline/
grill-me-codex · grill-with-docs-codex
+ Act 2: Codex reviews PLAN.md adversarially until APPROVED
codex linesecond model, high stakes
codex-review
plan already exists — cross-model review only·
codex-build
Act 3: Codex implements the frozen spec, Claude verifies diff + proof
program linetoo big for one wave
scale-check→
grill→
to-waves
preview gate · zero board writes until yes→
orchestrate-wave
per wave, often AFK→
wrapup→
retro
board lineit grew bottom-up
loose backlog→
board-to-waves
wave-stub candidates, no number yet→
to-prd
matures the stub→
to-issues
≥2 slices → promotes to a numbered wave anchor→
joins the program line
repair linesomething's broken
bug / anomaly→
diagnose
reproduce → isolate → fix → prove→
implement→
wrapup
structure linecode fights back
change fighting the codebase→
improve-codebase-architecture→
to-issues
plan a slice — or refactor in place
learn lineretro's real output
retro
user + agent friction, symmetric→
CLAUDE.md rule/
spec-self-critique layer · ADR/
memory/
board issue
per-patch approval · Meta section in PR body
Interchanges
a slice hinging on an unknown inserts verify-spike / decision-gate before its build
unclear path inserts prototype — throwaway that answers the design question first
inside implement, tdd runs red → green → refactor at pre-agreed seams
before every PR, local-ci runs the full gate; the pre-commit / pre-push hooks fire automatically once installed
lost? ask-matt routes you to the right skill
one-time setup, off-map: setup-workflow git-guardrails setup-pre-commit