crank
Crank Skill
Quick Ref: Autonomous epic execution.
/swarmfor each wave with runtime-native spawning. Output: closed issues + phase-2 handoff for/validate.
YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.
Loop position
Move 5 (wave execution) of the operating loop. Consumes the slice validation plan; produces wave-by-wave slice completion via /swarm + /implement. Hard gate at wave start: every row of the wave-validity check must pass (distinct write scopes, no shared migration/contract/CLI surface, declared integration order, owner per slice, discard path per slice). Any failed row → run those slices sequential, not parallel. Coupled-chain rule: two slices that both regenerate a shared derived surface (cli-command-surface / registry.json / context-map / codex manifest) collide even with disjoint source files — run them as a sequential chain, each link branched off the freshly-MERGED prior link. Parallelism is explicit ownership, not swarm chaos.
Autonomous execution: implement all issues until the epic is DONE.
Feed the orchestrator's re-plan loop — don't swallow findings into a silent retry. When run under /rpi, surface what a wave proved or broke UP to the orchestrator. A failed or surprising wave is re-plan input, not just a retry target: per the /rpi Agile Re-Plan Loop, the remaining waves may be refactored, inserted, dropped, or reordered before the next one runs. Re-cranking the same objective forever instead of letting the remaining plan change is the waterfall anti-pattern.
CLI dependencies: br (issue tracking, via BEADS_DIR="$(ao beads dir)" br), ao (knowledge flywheel). Both optional — see skills/shared/SKILL.md for fallback table. If br is unavailable, use TaskList for issue tracking and skip beads sync. If ao is unavailable, skip knowledge injection/extraction.
For Claude runtime feature coverage (agents/hooks/worktree/settings), the shared source of truth is skills/shared/references/claude-code-latest-features.md, mirrored locally at references/claude-code-latest-features.md.