---
description: Multi-agent review — spawns domain-specific review agents in parallel and consolidates findings
---

# Plenum: Multi-Agent Review Orchestrator

You are the Plenum orchestrator. Your job is to coordinate multiple specialist review agents to produce a comprehensive, consolidated review of the AstroDeck project.

## Step 1: Clarify Scope

Ask the user what they want reviewed. Options:
- **Whole project** — full review of all pages and components
- **Specific page** — e.g., "review the pricing page"
- **Component** — e.g., "review the Hero component"
- **Git diff** — review only what changed since last commit (run `git diff` to get the scope)
- **Performance issue** — focused performance investigation
- **Explicit "all"** — all 6 agents regardless of scope

If the user already specified the scope in their message, skip the question and proceed.

## Step 2: Select Agents Based on Scope

Choose agents automatically based on what is being reviewed:

| Scope | Agents |
|---|---|
| CSS/style changes | design-review, a11y-review, code-review |
| New page | ALL 6 agents |
| Content changes | seo-review, a11y-review |
| Component | design-review, ux-review, a11y-review, code-review |
| Performance issue | perf-review, code-review |
| Explicit "all" | ALL 6 agents |
| Whole project | ALL 6 agents |

## Step 3: Spawn Agents in Parallel

For each selected agent, use the **Agent tool** to spawn a subagent. Pass each agent:

1. The agent definition file path (e.g., `.claude/agents/design-review.md`)
2. The review scope (which files/pages/components to examine)
3. A list of the specific files relevant to the scope

Spawn all selected agents in parallel — do not wait for one to finish before starting another.

Each agent will:
- Read AGENTS.md for project conventions
- Read its specific globals files
- Analyze the scope
- Return findings in the standard format (Critical / Important / Nice-to-have / Positive)

## Step 4: Consolidate Results

Once all agents have reported back, produce a consolidated report:

### 4a: Identify Overlaps
When multiple agents flag the same issue, merge them into a single finding and note which disciplines identified it. This strengthens the case for fixing it.

### 4b: Detect Conflicts
When agents disagree (e.g., UX wants an animation, Perf wants to remove it), present both sides clearly:

```
### Conflict: [Topic]
- **[Agent A]**: [Their position and reasoning]
- **[Agent B]**: [Their position and reasoning]
- **Trade-off**: [What the user needs to decide]
- **Recommendation**: [Your suggested resolution, if any]
```

### 4c: Prioritize by Impact
Order findings by impact:
1. Critical findings (blocks users, breaks functionality, fails compliance)
2. Important findings (degrades quality, inconsistency, maintenance risk)
3. Nice-to-have (polish, optimization, best practices)

## Step 5: Write Report

Write the consolidated report to `system/reports/plenum-[YYYY-MM-DD].md` using this format:

```markdown
# Plenum Review — [YYYY-MM-DD]

## Scope
[What was reviewed]

## Agents
[Which agents participated]

## Summary
[2-3 sentence executive summary of overall quality and top priorities]

## Critical Findings
[Merged critical findings from all agents, with source agents noted]

## Important Findings
[Merged important findings]

## Conflicts & Trade-offs
[Any conflicts between agent recommendations]

## Nice-to-have
[Lower priority improvements]

## Positive Highlights
[What the project does well — consolidated from all agents]

---
*Generated by Plenum multi-agent review*
```

## Step 6: Present to User

After writing the report:
1. Display the summary and critical findings directly in the conversation
2. Link to the full report file
3. Ask the user which findings they want to address
4. **Do NOT auto-implement anything** — the user decides what to fix and when

## Important Rules

- **Never auto-implement**: The Plenum review is advisory only. No code changes.
- **Respect conflicts**: When disciplines disagree, present both sides and let the user decide. Do not silently pick a winner.
- **Be concise**: The consolidated report should be shorter than the sum of individual reports. Merge duplicates, cut redundancy.
- **Date the report**: Always use today's date in the filename and report header.
