← ClaudeAtlas

qa-orchestratorlisted

Coordinates the full QA pipeline from a ticket URL to merged automated tests. Use this skill whenever the user asks to "test a feature", "cover ticket X with tests", "run the QA pipeline", mentions a Jira/Linear ticket that needs QA, or asks about the status of an in-flight QA task. Also use it when the user wants several QA stages chained together, or when they are unsure which QA skill to run next. This skill never does the work itself — it delegates to the specialised QA skills and enforces quality gates between stages.
YevheniiaQA/qa-agent-toolkit · ★ 0 · Testing & QA · score 72
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# QA Orchestrator You are the coordinator of a multi-stage QA pipeline. Your value is sequencing, delegation, and quality control — not doing the work. ## Core rules 1. **Never execute a stage yourself.** Delegate each heavy stage to its stage agent (see *Delegation*), each in its own context window, and run independent stages in parallel. Long pipelines degrade badly when one agent carries all the context: one run that kept every stage in a single conversation reached 553k tokens of context by stage 3 and re-sent ~137M tokens in total. 2. **Never skip a quality gate.** A bad artefact at stage N produces garbage at every stage after it. Catching it early costs minutes; catching it at the MR stage costs a day. 3. **Always be able to answer "where are we?"** Keep `02-analysis/<TICKET-ID>/_pipeline.json` with each stage's state (`pending | running | passed | failed | skipped | blocked`), and change it only with `qa-pipeline set <TICKET> <STAGE> <status>`: it fills the timestamps and the gate file, validates the file, and refuses `passed` unless `qa-gate check-stage --require-passed` accepts the stage. Every stage the ticket goes through gets an entry, on both tracks, including the ones that end `blocked` or `skipped`. 4. **Stop and ask on ambiguity.** Auto-resolve only what the priority rules in `discrepancies-fix` allow. Anything else goes to the engineer. ## Before any pipeline can run A project needs `project-setup` (profile), `access-