How anasss/qa-orchestra works
QA Orchestra is a Claude Code toolkit of ten standalone QA agents. The usual workflow is a user invokes an agent with a PR, diff, acceptance criteria, or test request; the agent produces a Markdown report in qa-output/, which another agent can use for follow-up. The README also documents browser-based validation and an optional orchestrated pipeline. Agent prompts and data-flow links are mapped from the README; their implementation details were not sampled, so uncertain agent-to-agent handoffs are not expanded.
Main entry points: qa-output QA Output Reports · orchestrator.md Orchestrator · functional-reviewer.md Functional Reviewer · browser-validator.md Browser Validator
Components 15
Standalone QA
- Functional Reviewer
.claude/agents/functional-reviewer.md - Scenario Designer
.claude/agents/test-scenario-designer.md - Smart Test Selector
.claude/agents/smart-test-selector.md - Bug Reporter
.claude/agents/bug-reporter.md
Live Validation
- Environment Manager
.claude/agents/environment-manager.md - Browser Validator
.claude/agents/browser-validator.md
Pipeline and Release
- Orchestrator
.claude/agents/orchestrator.md - Release Analyzer
.claude/agents/release-analyzer.md - Automation Writer
.claude/agents/automation-writer.md - Manual Validator
.claude/agents/manual-validator.md
Other components
- User
- Project Context
context/CONTEXT.md - QA Output Reports
qa-output - MCP Servers
- Claude Code
Connections 31
- User → Claude Code: invokes
README.md - Claude Code → Functional Reviewer: runs agent
README.md - Claude Code → Scenario Designer: runs agent
README.md - Claude Code → Smart Test Selector: runs agent
README.md - Claude Code → Bug Reporter: runs agent
README.md - Claude Code → Environment Manager: runs agent
README.md - Claude Code → Browser Validator: runs agent
README.md - Claude Code → Orchestrator: runs agent
README.md - Claude Code → Release Analyzer: runs agent
README.md - Claude Code → Automation Writer: runs agent
README.md - Claude Code → Manual Validator: runs agent
README.md - Functional Reviewer → QA Output Reports: writes report
README.md - Scenario Designer → QA Output Reports: writes report
README.md - Smart Test Selector → QA Output Reports: writes report
README.md - Bug Reporter → QA Output Reports: writes report
README.md - Environment Manager → QA Output Reports: writes report
README.md - Browser Validator → QA Output Reports: writes report
README.md - Orchestrator → QA Output Reports: writes report
README.md - Release Analyzer → QA Output Reports: writes report
README.md - Automation Writer → QA Output Reports: writes output
README.md - Manual Validator → QA Output Reports: writes report
README.md - Project Context → Environment Manager: describes setup
README.md - MCP Servers → Browser Validator: enables browser
README.md - MCP Servers → Functional Reviewer: provides PR data
README.md - MCP Servers → Release Analyzer: provides repo data
README.md - Orchestrator → Functional Reviewer: routes workflow
README.md - Orchestrator → Scenario Designer: routes workflow
README.md - Orchestrator → Browser Validator: routes workflow
README.md - Orchestrator → Release Analyzer: routes workflow
README.md - QA Output Reports → Functional Reviewer: feeds follow-up
README.md - QA Output Reports → Bug Reporter: feeds follow-up
README.md