| name | brooks-harness |
| description | Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + README + CHANGELOG + AGENTS/GEMINI in sync, audit trigger... |
| risk | unknown |
| source | https://github.com/hyhmrright/brooks-lint/tree/main/.claude/skills/brooks-harness |
| source_repo | hyhmrright/brooks-lint |
| source_type | community |
| date_added | 2026-07-01T00:00:00.000Z |
| license | MIT |
| license_source | https://github.com/hyhmrright/brooks-lint/blob/main/LICENSE |
brooks-lint — Maintenance Harness (Orchestrator)
When to Use
Use this skill when you need maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + README + CHANGELOG + AGENTS/GEMINI in sync, audit trigger...
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 under _workspace/brooks-harness/. The real
artifacts are the repo files themselves — agents edit skills/, evals/, manifests
directly; _workspace/ only holds the run's notes and the PASS/FAIL verdict for audit.
Phase 1 — Classify the request
Pick the minimal set of stages. The QA stage is never skipped — every change is
gated.
