brooks-harness

# brooks-lint — Maintenance Harness (Orchestrator) This skill orchestrates work **on the brooks-lint repo itself**. It runs a sequential subagent pipeline: each stage is a dedicated agent defined in `.claude/agents/`. Spawn each with the `Agent` tool, `subagent_type` set to the agent name, and **always `model: "opus"`**. Stages depend on each other in order, so this is a pipeline, not a parallel team. ## Pipeline ``` [orchestrator] Phase 0 context check Phase 1 classify request → select stages Phase 2 run selected stages in order, with a QA loop-back: skill-author → eval-curator → consistency-qa ─(FAIL)→ back to author │ PASS ▼ trigger-boundary-auditor (only if a description changed) ▼ release-manager (only if release requested) Phase 3 report + collect feedback ``` ## Phase 0 — Context check Determine the run mode before doing anything: - `_workspace/brooks-harness/` exists + maintainer asks to redo part of a prior run → **partial re-run**: invoke only the affected stage(s), reusing prior notes. - `_workspace/brooks-harness/` exists + a fresh request → **new run**: move the old folder to `_workspace/brooks-harness_prev/`, start clean. - No `_workspace/brooks-harness/` → **initial run**: create it. Run notes and the QA report live und...