QA Orchestra
10 standalone QA agents for Claude Code. Each one answers a specific question about your PR — does this diff implement the AC?, what scenarios do I need?, which of my tests will break? — and writes a Markdown report you can paste into GitHub or Jira.
Two layers: the agents bring QA expertise (diff vs AC analysis, scenario design, test selection). MCP brings the data (GitHub, Chrome DevTools, Jira, GitLab). Your context/CONTEXT.md describes your stack in one file.
No SaaS. No API keys beyond Claude. Works with any stack.
Install
Option A: Plugin install (recommended)
In any Claude Code chat, run:
/plugin marketplace add Anasss/qa-orchestra
/plugin install qa-orchestra@qa-orchestra
/reload-plugins
Or use the UI: Customize → Manage plugins → Marketplaces tab → paste Anasss/qa-orchestra → Add → Plugins tab → Install.
Once installed, all 10 agents are available. Type @functional-reviewer, @orchestrator, etc.
What the install looks like in Claude Code
Option B: Global agents (available in all projects)
# Clone and copy agents to your global directory
git clone https://github.com/Anasss/qa-orchestra.git
cp qa-orchestra/.claude/agents/*.md ~/.claude/agents/
Option C: Clone into your workspace
# 1. Clone alongside your project repos
git clone https://github.com/Anasss/qa-orchestra.git
cd qa-orchestra
# 2. Fill in your project context
cp examples/CONTEXT.example.md context/CONTEXT.md
# Edit context/CONTEXT.md with your stack, repos, URLs, and commands
# 3. Open Claude Code — agents auto-load from .claude/agents/
claude
What It Does
Pick one agent for one question. @functional-reviewer is the most common entry point:
You: @functional-reviewer Compare PR #42 against these ACs:
AC-1: users can add items to the cart from the product listing page
AC-2: the cart count in the nav header updates immediately after adding
QA Orchestra writes qa-output/functional-review.md:
- AC-1: COVERED at src/components/quick-add-button.tsx:43
- AC-2: AT RISK — no router.refresh() after the server action
- 2 regression risks in unchanged code paths touched by the diff
- Verdict: GAPS — needs browser validation on AC-2
One agent. One question. One Markdown file you can paste into GitHub or Jira.
Other standalone entry points:
@test-scenario-designer — generate test scenarios from acceptance criteria (happy, negative, boundary, edge)@smart-test-selector — map a diff to your existing tests; find what to run, what may break, and where coverage is missing@bug-reporter — turn findings into developer-ready bug reports
Each runs independently. None requires the orchestrator or a prior agent. For the full pipeline (@orchestrator), see the recipe table below — most users never need it.
Every agent writes to qa-output/. The next agent reads from there. No copy-pasting between agents.
Not in scope: code quality review, linting, security scanning, performance profiling, or unit-test generation. QA Orchestra is scoped to functional correctness against acceptance criteria.
Agents
QA Orchestra ships 10 agents organized by how you'll actually use them. Most users live in Tier 1. You can stop reading after the first table if you want — everything below it is optional.
Tier 1 — Standalone use cases (start here)
These four agents are the daily drivers. Each answers one question, runs independently, and produces a Markdown file you can paste into GitHub, Jira, or Linear.
| Agent | Model | Answers the question |
|---|
| functional-reviewer | Opus | Does this diff actually implement the acceptance criteria? Where are the gaps and risks? |
| test-scenario-designer | Sonnet | What test scenarios do I need to cover this AC? Happy path, negative, boundary, edge. |
| smart-test-selector | Sonnet | Which of my existing tests does this diff affect? What's likely to break? Where are my coverage gaps? |
| bug-reporter | Sonnet | Turn these findings into developer-ready bug reports. |
Tier 2 — Live validation chain
These two agents work together to test the feature in a real browser, not just read the diff. They're what separates QA Orchestra from static AI review tools.
