Add qa-orchestra QA lifecycle agents

[Anasss]

Summary

Adds 5 QA lifecycle agents from qa-orchestra, a coordinated 10-agent QA toolkit for Claude Code:

• functional-reviewer — Compares code diffs against acceptance criteria to find gaps
• test-scenario-designer — Generates test scenarios from AC (happy path, negative, boundary, edge cases)
• bug-reporter — Converts QA findings into structured, developer-ready bug reports
• automation-writer — Turns test scenarios into executable Playwright/Cypress test code
• qa-orchestrator — Routes QA tickets to the right agents in the right order

These agents work together via output chaining — each agent writes to a file that the next agent reads. The orchestrator coordinates the full pipeline.

See the full 10-agent set (including environment-manager, manual-validator, and browser validation) at https://github.com/Anasss/qa-orchestra

[greptile-apps]

Greptile Summary

This PR adds five QA lifecycle agent markdown files (functional-reviewer, test-scenario-designer, bug-reporter, automation-writer, qa-orchestrator) from the qa-orchestra toolkit. Three of the five files are internally consistent and well-scoped. However, qa-orchestrator.md contains two logic errors that affect the execution model's correctness: an inaccurate parallelism claim and references to a non-existent agent, the latter of which also bleeds into bug-reporter.md.

Confidence Score: 4/5

Not safe to merge as-is; two P1 logic errors in the orchestrator layer produce incorrect execution plans.

Three of five files are well-structured and have no issues. The score is 4 rather than 5 because qa-orchestrator.md contains two P1 defects: a factually wrong parallelism claim that misdescribes functional-reviewer's required inputs, and references to a browser-validation agent that does not exist, causing the full QA pipeline route to be unexecutable. bug-reporter.md inherits the second issue. Both are correctness problems in the stated execution model, not style suggestions.

qa-orchestrator.md needs both logic fixes; bug-reporter.md needs the browser-validation reference removed or annotated.

Important Files Changed

Filename	Overview
content/04-quality-security/automation-writer.md	Adds automation-writer agent for generating Playwright/Cypress/Gherkin test code; well-structured with clear AAA, locator, and data-driven principles. No issues found.
content/04-quality-security/bug-reporter.md	Adds bug-reporter agent for structured bug reports; step 1 references a non-existent browser-validation agent as an input source, creating a broken dependency.
content/04-quality-security/functional-reviewer.md	Adds functional-reviewer for AC-vs-diff gap analysis with a clear five-check framework and precise output format. No issues in this file itself.
content/04-quality-security/qa-orchestrator.md	Orchestrator agent has two P1 logic issues: incorrect parallelism claim (functional-reviewer needs AC + diff, not just AC), and references to a non-existent browser-validation agent that breaks the full pipeline route.
content/04-quality-security/test-scenario-designer.md	Adds test-scenario-designer with six mandatory design techniques and a complete output format (scenario table, AC matrix, test data, risks). Well-defined and self-consistent.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    ORC[qa-orchestrator]
    ORC -->|Review this ticket| FR[functional-reviewer\nNeeds: AC + diff]
    FR -->|gaps found| BR[bug-reporter]
    ORC -->|Create test cases| TSD[test-scenario-designer\nNeeds: AC only]
    ORC -->|Automate scenarios| AW[automation-writer]
    TSD --> AW
    ORC -->|Test this PR| PAR{Parallel?}
    PAR -->|claimed: both need AC only\n❌ FR also needs diff| FR2[functional-reviewer]
    PAR --> TSD2[test-scenario-designer]
    FR2 --> BR2[bug-reporter]
    TSD2 --> AW2[automation-writer]
    ORC -->|Full QA pipeline| FULL[All agents]
    FULL --> MISSING[❌ browser-validation\nAgent does not exist]

Loading

_{Reviews (1): Last reviewed commit: "Add qa-orchestrator agent from qa-orches..." | Re-trigger Greptile}