Coordinate qa-lead and qa-tester to generate test plans, cases, and sign-off reports.
npx skills add https://github.com/solace-ill/vector-flow --skill team-qa-solace-ill
Please help me install this Agent Skill. Skill: team-qa Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/team-qa Command: npx skills add https://github.com/solace-ill/vector-flow --skill team-qa-solace-ill
Orchestrate the QA team through a full testing cycle to ensure coordinated planning, execution, and sign-off for sprints or features.
Invoke the skill with a sprint identifier or feature name to start the QA cycle and let the system spawn the qa-lead and qa-tester subagents.
High-intent search queries and answers about installing and using this skill.
To coordinate a QA cycle from strategy to sign-off, you need a system that orchestrates test plan generation, test case writing, smoke checks, execution, and reporting across stories. This requires clear story inputs, stage information, and acceptance criteria to generate complete QA artifacts.
Generating a test plan and test cases for a sprint requires clear story inputs, stage information, and acceptance criteria. Providing these inputs allows a coordinated QA system to produce a complete testing package, including strategy and execution artifacts.
Yes, this approach applies to both automated and manual testing execution. It coordinates the delegation of tasks to generate test cases, run smoke checks, and produce bug reports, ensuring full coverage across your sprint or feature cycle.
The best way to manage QA sign-off and traceability across stories is to generate a centralized sign-off report after executing test plans. This ensures coordinated planning and provides clear traceability for all sprint or feature testing artifacts.
No, this QA automation approach requires clear story inputs and predefined acceptance criteria to function correctly. Without these essential inputs, the system cannot accurately generate a tailored test strategy, plan, or specific test artifacts.
Using a coordinated QA system instead of managing manual testing separately ensures synchronized planning, task delegation, and sign-off reporting. It provides centralized traceability across stories, preventing isolated testing efforts and ensuring complete coverage.
imclabGenerate structured QA test plans from sprint stories and GDD acceptance criteria.
Euraika-LabsOrchestrates end-to-end sprint QA with smoke checks, test plans, and sign-off reports.
u9401066Automate Git commit, push, and CI workflow triggering with pre-push validation.
cenconq25Coordinate end-to-end QA workflows for sprint or feature sign-off.
