| name | execute-qa |
| description | Execute quality assurance validation for implemented features against PRDs, TechSpecs, and task files. Use when Codex is asked to run QA, validate an implementation, verify requirements, run E2E tests with Playwright MCP, check accessibility, perform visual checks, document bugs, create bugs.md, or create qa.md under tasks/prd-[feature-name]/. |
Execute QA
Core Workflow
Use this skill to validate an implemented feature against its PRD, TechSpec, and Tasks, then produce QA and bug reports in the project task structure.
Read resources/execute-qa.md before starting. Treat that file as the canonical workflow for this skill.
Load resources/qa-report-template.md only when generating qa.md. Treat that file as the required QA report template standard.
Execution Rules
- Confirm and read the PRD at
tasks/prd-[feature-name]/prd.md.
- Confirm and read the TechSpec at
tasks/prd-[feature-name]/techspec.md.
- Confirm and read Tasks at
tasks/prd-[feature-name]/tasks.md.
- Extract and verify all PRD and TechSpec requirements before approving QA.
- Use Playwright MCP for all browser interactions and E2E validation.
- Check accessibility against WCAG 2.2 expectations.
- Capture evidence screenshots for tested flows and all bugs.
- Check browser console messages and network requests where relevant.
- Generate
bugs.md under the feature folder when bugs are found.
- Generate
qa.md from the exact template in resources/qa-report-template.md.
- Approve QA only when all requirements pass.
Expected Inputs
Typical input is a feature directory, feature name, or request such as:
- "Use $execute-qa for tasks/prd-team-invitations."
- "Run QA for the checkout-flow implementation."
- "Validate this feature against its PRD, TechSpec, and tasks."
If the feature directory is unclear, inspect tasks/prd-* directories and ask for clarification only when multiple plausible feature folders exist.
