agentleFS
mnzraleemnzralee/claude-multi-agent-architecture/.claude/skills/review-board/SKILL.md

review-board

Skill8 starsChanged 45 days agoMITView on GitHub

Run the multi-wave Software Engineering Review Board (SERB) over a proposed plan before execution. A read-only board of specialist agents gathers ground truth, critiques from architecture/testing/security/devops/quality lenses, then synthesizes a refined, executable plan with a go/no-go. Use for high-stakes or cross-cutting plans, or when the developer asks to "review the plan", "run the review board", or "SERB this".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every agent reads actual files, not just the plan summary.

    line 35
  2. Distinctive:

    Do not execute the plan. Return the full review plus the refined plan.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Software Engineering Review Board (SERB)

A rigorous, multi-wave plan review. Gather verified ground truth, critique from five specialist lenses in parallel, then synthesize one refined plan with a go/no-go. Every reviewer is read-only; the board advises, it does not implement.

When to use

Invoke /review-board (or paste .claude/prompts/review-board.md after a plan in plan mode) when:

  • The plan is high-stakes (touches auth, money, migrations, production, or a wide blast radius).
  • The change is cross-cutting and a surface decision would miss ripples (pair with .claude/rules/depth-first-impact-analysis.md).
  • You want an enterprise-grade refinement of a plan before committing to execution.

Skip it for one-sentence changes; the cost is not worth it there (see .claude/rules/ai-orchestration-decision-gate.md).

How to run

The full agent specifications live in .claude/prompts/review-board.md. Read that file and execute it against the current plan. In brief, it is three waves:

  1. Wave 1: Discovery (4 parallel, read-only) gathers ground truth, not critique:
    • Codebase Deep Explorer (actual paths, selectors, endpoints versus the plan's assumptions)
    • Best-Practices Researcher (current standards and pitfalls per technology, via WebSearch)
    • Live-State Verifier (real, non-mutating checks of what is actually up)
    • Dependency & Risk Mapper (dependency graph, failure modes, hidden assumptions, rollback)
  2. Wave 2: The Board (5 parallel specialists, read-only) critiques against the Wave 1 ground truth: Chief Architect, Testing & Reliability Lead, Security & Compliance Lead, DevOps & Infrastructure Lead, Quality & Standards Lead. Each returns CRITICAL/HIGH/MEDIUM/LOW findings with file:line evidence and the fix.
  3. Wave 3: Synthesis deduplicates and ranks findings, resolves conflicts using ground truth, and delivers the aggregate findings table, the refined executable plan, a Go/No-Go (GREEN/YELLOW/RED), and a quality scorecard.

Rules

  • Wave 1 completes before Wave 2 launches (the board needs verified facts). Within a wave, run agents in parallel.
  • Every agent reads actual files, not just the plan summary. Best-practice research and live-state checks are required.
  • Single-writer, many-readers: every reviewer is read-only. The board does not implement. After approval, exactly one agent executes the refined plan.
  • Findings meet the evidence bar in .claude/rules/deterministic-review.md: every finding cites real code or a real source, never an assumption. If the plan is already strong, say so plainly rather than manufacturing objections.
  • Do not execute the plan. Return the full review plus the refined plan; the human decides when to go.

Related

  • .claude/prompts/review-board.md, the full agent specifications to execute
  • .claude/rules/deterministic-review.md, the evidence bar every finding must meet
  • .claude/rules/depth-first-impact-analysis.md, the cross-layer ripple trace the architect lens applies
  • .claude/rules/ai-orchestration-decision-gate.md, when a board is worth the cost
  • .claude/agents/evaluator.md, the lighter-weight single-critic alternative for smaller artifacts

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.