crew-configlisted

# crew Config & Registry crew is **config-driven**: behavior comes from `config.json`, layered **defaults < global (`~/.claude/crew/config.json`) < project (`.planning/config.json`)**. There is no compiled validator — these schemas are the contract; write valid JSON. ## `config.json` (full defaults) ```jsonc { "crewVersion": null, // crew plugin version this config was last reconciled with; set by /crew:init & /crew:setup, checked on session start // ── workflow: the steps, as first-class objects ──────────────────────────── // Two levels (see "Workflow model" below): workflow.mode advances the *step* // chain (brief→…→complete); each gateable step's `run` decides how it's handled // when the chain reaches it. "workflow": { "mode": "manual", // "manual" | "auto" — Level 1: manual = do the one called step and stop (run-gates dormant); auto = walk the chain, each step firing per its run "brief": { // always interactive — no run gate (see "Safety boundary") "depth": "normal", // "light" | "normal" | "deep" — how broad (coverage) "intensity": "normal" // "gentle" | "normal" | "brutal" — how hard Roast-Me pushes back }, "plan": {}, // always interactive — no run gate "execute": { "parallel": "auto", // "auto" | "manual" | "off" — strategy granularity: phases serial vs parallel (worktrees) "loop": "all",