Orchestrate a complete QA testing cycle for sprint or feature workflows.
npx skills add https://github.com/imclab/xrA1-swarm --skill team-qa-imclab
Please help me install this Agent Skill. Skill: team-qa Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/team-qa Command: npx skills add https://github.com/imclab/xrA1-swarm --skill team-qa-imclab
team-qa removes the chaos of ad-hoc testing by orchestrating a full QA workflow—strategy, test planning, manual execution, and sign-off—so sprints ship with clear coverage and documented outcomes.
Run team-qa for your next sprint by invoking it with the argument sprint-03 (or feature: system-name) and approve each phase when prompted.
High-intent search queries and answers about installing and using this skill.
A complete sprint QA cycle coordinates strategy, smoke checks, test plan creation, manual execution, and sign-off reporting. It classifies stories into test-relevant categories and enforces smoke-check gates to ensure clear coverage and documented outcomes.
Story classification in sprint validation categorizes stories into types like Logic, Integration, Visual/Feel, UI, and Config/Data. This determines which parts require automated evidence versus manual QA, directly shaping the generated test plan and execution scope.
You enforce a smoke testing gate by performing an initial check that yields a PASS, PASS WITH WARNINGS, or FAIL verdict. This result controls whether the QA cycle proceeds to manual test execution and subsequent phase transitions.
Yes, QA orchestration applies directly to story-file driven development workflows. It loads stage-aware context to determine test scope, produce test cases, perform manual validation, and file bugs, generating persistent QA artifacts under the production/qa/ directory.
You generate persistent QA artifacts by compiling final coverage and bug outcomes into a sign-off report. The workflow produces these test plans and bug reporting outputs under the production/qa/ directory for documented sprint validation.
The best way to structure bug reporting is by coordinating test case writing with targeted bug filing within an orchestrated cycle. This links bug reports directly to classified story scopes and final sign-off coverage metrics.
CarlosQ96Generate structured QA plans from GDDs and story files.
polseguCoordinate QA teams to generate test plans, cases, and sign-off reports.
ajianazOrchestrate QA testing workflows from strategy design to metrics reporting.
sumilee-pcuCoordinate QA subagents for strategy, test case generation, and bug reporting.
