Verify executed command outcomes against linked acceptance criteria.
npx skills add https://github.com/anderson-joyle/claude-a-team --skill qa-anderson-joyle
Please help me install this Agent Skill. Skill: QA Source: https://github.com/anderson-joyle/claude-a-team/tree/main/skills/qa Command: npx skills add https://github.com/anderson-joyle/claude-a-team --skill qa-anderson-joyle
It prevents unverified changes from moving forward by checking real execution evidence against the acceptance criteria defined earlier in the workflow.
Run the QA step after you have execution results and artifacts from Engineer and ask the workflow to verify acceptance criteria using the provided evidence.
High-intent search queries and answers about installing and using this skill.
To validate execution results against acceptance criteria, you compare actual command outcomes and observed results to linked test scenarios. This evidence-based validation checks real execution artifacts to ensure software changes meet defined requirements before moving forward.
Evidence-based validation in software workflows is the process of verifying executed commands and observed outcomes against linked acceptance criteria. It requires actual execution results and artifacts to prevent unverified changes from progressing, ensuring traceability and auditability.
You map pass/fail judgments to acceptance criteria IDs by linking validation outcomes directly to the original criteria defined earlier in the workflow. This ensures traceability and auditability when verifying executed command outcomes against test scenarios.
Yes, you can use execution artifacts to flag regression risks and coverage gaps. The validation process assesses provided artifacts and evidence to identify potential regressions, ensuring only verified changes move forward without fabricating execution results.
If acceptance criteria were not actually tested, the validation process refuses to approve them. Safety guardrails prohibit fabricating execution results or approving criteria that lack evidence-backed pass/fail/inconclusive judgments from real command outcomes.
Before running QA validation, you need PM context, Architect/Security context, Review decisions, Engineer execution handoff, and actual execution results. These artifacts provide the acceptance criteria and evidence required to verify software changes.
JongHyunLee84Execute end-to-end tests against acceptance criteria and classify failures.
GDSDNOrchestrate a multi-phase QA review process for software builds and emit an APPROVE/REJECT signal.
CaptainCrouton89Automate software tests to verify functionality against acceptance criteria.
benredmondTranslate plans into runnable code and validate against acceptance criteria.
