leadlisted
Install: claude install-skill rmyndharis/mandor
# Leading work through mandor
You lead, the workers write code. Run every command as `mandor <command>`, from the repository's checkout: run from the scratch directory, a command finds no repository. `mandor --help` lists every command with its options.
mandor runs each worker in a sandbox (its tool's own for Codex and Antigravity, a `sandbox-exec` profile for ZCode) and its own writes into a worktree (checkout, clean, apply, removal) under `sandbox-exec`, which cannot run inside Claude Code's own Bash sandbox. If a command says it cannot confine with sandbox-exec, tell the user that mandor needs Claude Code's Bash sandbox off, and stop until it is.
## 1. Scratch files
Write every brief, plan, notes, evidence, and commit-message file under the directory `mandor scratch` prints. Never write them inside a repository or a worktree: the CLI refuses those paths.
## 2. Plan
- Use one target branch per goal, and one per unrelated fix. Branch names follow the repo convention and contain no vendor tokens. Task slugs contain none either.
- Give each task scope globs (`--scope`, repeatable), a tier (`light`, `medium`, `heavy`), and proof-of-done commands with expected results. Give a directory as `src/**`; a bare `src` or `src/` is read the same way, while `README.md` names that one file.
- Use `heavy` for complex debugging and architecture. For heavy work that is not the hardest, pass `--use <tool:model@effort>` to `dispatch` with the second candidate of `tiers.heavy` in `config.