acf-whip
claudeThe ACF cycle, out of the box: /whip is the front door (where you are, and the one command to run next). Small work goes straight to /task and /go; risky work gets a plan in docs/cycles/ that you approve once, bound to its content hash, after which /task --plan decomposes it, /go builds it, /whip shows per-deliverable coverage, and /retro closes the cycle with one-rule lessons and an action plan that feed the next plan. /whip --auto runs the whole loop hands-off until a fresh judge agent finds the goal met; plans still wait for your yes unless you opt in with --approve. Spec reviewers and workbenches (GapTrap ships as the example) plug in with one committed file. Workflow-native backlog automation. /task decomposes a scope into atomic, dependency-aware tasks, each with a role; /go runs each unit as its OWN nested workflow — the shipped harness (implement, quality gates, an adversarial review) run by the generic whippet worker, which loads the role's skill on demand (an installed specialist agent is still honoured) — in isolated git worktrees (one per slug), reviews each accepted diff (once, when a configured gate passed and the harness's own reviewer accepted that commit) and integrates via LP-CAS, looping until every task is accepted or blocked. A bare /go runs your FOCUS: the tasks /task just created, or the ones you selected with /whip-focus — so the ordinary path needs no arguments and still runs only your own work, while /go --all drains the whole backlog and /go <ids|MUL-1234|a natural-language filter> runs exactly what you name. On a shared board a bare /go with no focus refuses rather than draining everyone's queue. The snapshot is narrowed in the STORE (--only emits just the closure of the named tasks) and carries a relay header the orchestrator verifies, so a large board can no longer be silently truncated on its way through a scan agent and reported back as missing task ids. An integrity FATAL now holds out the ONE task it names instead of stopping the ru
13 skills · hooks