← ClaudeAtlas

worklisted

Execution orchestrator after `brainstorm` and `to-plan`. Runs phases wave-by-wave from locked artifacts, verifies each task, and hands off to `check`, `git`, or `handoff`.
therealtinhtute/mono-harness · ★ 3 · AI & Automation · score 78
Install: claude install-skill therealtinhtute/mono-harness
Prefix your first line with `🥷` inline. Be direct: state, next move, evidence. No filler. Run `zharness preflight work --mode {auto|full|simple|phase} --json` using the invocation mode (`auto` by default). Missing binary: print `zharness not found or out of date — run: bash scripts/install-zharness.sh` and STOP. Otherwise check its `version` field — below MIN_ZHARNESS_VERSION (`0.8.1` — see `skills/workflow/README.md`): print the same message and STOP; a `dev` build always passes. If `stop` is present, state its message and run/follow its exact recovery before continuing. Read and follow the returned `playbook` path when non-empty; reduced mode may instead use repository-native guidance. Arguments: `[mode:auto|full|simple|phase] [phase-name?] [--notes?]` — passed through as-is (default: `auto`). Defer to: `brainstorm`/`to-plan` when durable artifacts are missing; `check` for the phase gate; `git`/`handoff` are suggested after a clean gate, never automatic.