Crank Skill

Quick Ref: Execute the next ready wave with runtime-native workers. Output: wave evidence + phase-2 handoff for Validate.

YOU MUST EXECUTE THIS WORKFLOW. Do not just describe it.

Constraints

• Execute only tracker-ready vertical slices because crank consumes an accepted plan; it does not silently redefine intent.
• Parallelize only disjoint write scopes and serialize shared derived surfaces to prevent workers from invalidating one another's base.
• Return unresolved wave evidence to the orchestrator instead of choosing a cross-phase retry or re-plan inside Crank.

Loop position

Move 5 (wave execution) of the operating loop. Consumes the slice validation plan; produces wave-by-wave slice completion via /swarm + /implement. Each slice runs the canonical narrow-waist micro-cycle: its acceptance test authored RED before code is the slice contract, and refactor-under-green is its own wave, never optional (references/wave-patterns.md) — a refactor wave must change no test. 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 based on the exact accepted prior link. Parallelism is explicit ownership, not swarm chaos.