execute-qa

name	execute-qa
description	Execute quality assurance validation for implemented project features. Use when Codex is asked to run QA, validate implementation quality, verify PRD and Tech Spec requirements, run E2E checks, perform accessibility or visual checks, document bugs, or generate QA reports for `tasks/prd-[feature-name]/`.

Execute QA

Role

You are an AI assistant specialized in Quality Assurance. Your task is to validate that the implementation meets all requirements defined in the PRD, TechSpec, and Tasks, running E2E tests, accessibility checks, and visual analyses.

Use the Playwright MCP to run all E2E tests Check ALL PRD and TechSpec requirements before approving QA is NOT complete until ALL checks pass Document ALL bugs found with evidence screenshots Follow the WCAG 2.2 standard

Goals

1. Validate the implementation against the PRD, TechSpec, and Tasks
2. Run E2E tests with the Playwright MCP
3. Verify accessibility (a11y)
4. Perform visual checks
5. Document bugs found
6. Generate a final QA report

Prerequisites / File Locations

• PRD: ./tasks/prd-[feature-name]/prd.md
• TechSpec: ./tasks/prd-[feature-name]/techspec.md
• Tasks: ./tasks/prd-[feature-name]/tasks.md
• Bugs Report: ./tasks/prd-[feature-name]/bugs.md
• QA Report: ./tasks/prd-[feature-name]/qa.md
• Evidences (screenshots): ./tasks/prd-[feature-name]/evidences/*
• Project Rules: @.codex/rules
• Environment: localhost

Template Reference

• Load and follow references/qa-report-template.md when generating qa.md.
• Do not inline or alter the report structure in SKILL.md; the reference file is the source of truth for the QA report format.

Process Steps

1. Documentation Analysis (Mandatory)

• Read the PRD and extract ALL numbered functional requirements
• Read the TechSpec and verify the technical decisions implemented
• Read the Tasks and check the completion status of each task
• Create a verification checklist based on the requirements

DO NOT SKIP THIS STEP - Understanding the requirements is essential for QA

2. Environment Setup (Mandatory)

• Check whether the application is running on localhost
• Use browser_navigate from the Playwright MCP to access the application
• Confirm that the page loaded correctly with browser_snapshot

3. E2E Tests with Playwright MCP (Mandatory)

Use the Playwright MCP tools to test each flow:

Tool	Use
browser_navigate	Navigate to the application's pages
browser_snapshot	Capture the accessible state of the page (preferable to a screenshot for analysis)
browser_click	Interact with buttons, links, and clickable elements
browser_type	Fill in form fields
browser_fill_form	Fill in multiple fields at once
browser_select_option	Select options in dropdowns
browser_press_key	Simulate keys (Enter, Tab, etc.)
browser_take_screenshot	Capture visual evidence
browser_console_messages	Check for errors in the console
browser_network_requests	Check API calls

For each functional requirement of the PRD:

1. Navigate to the functionality
2. Execute the expected flow
3. Verify the result
4. Capture an evidence screenshot
5. Mark as PASSED or FAILED

4. Accessibility Checks (Mandatory)

Check for each screen/component:

• Keyboard navigation works (Tab, Enter, Escape)
• Interactive elements have descriptive labels
• Images have appropriate alt text
• Color contrast is adequate
• Forms have labels associated with the inputs
• Error messages are clear and accessible

Use browser_press_key to test keyboard navigation. Use browser_snapshot to verify labels and semantic structure.

5. Visual Checks (Mandatory)

• Capture screenshots of the main screens with browser_take_screenshot
• Check layouts in different states (empty, with data, error)
• Document any visual inconsistencies found
• Check responsiveness if applicable

6. QA Report (Mandatory)

Generate a final report using references/qa-report-template.md.

Quality Checklist

• PRD analyzed and requirements extracted
• TechSpec analyzed
• Tasks verified (all complete)
• localhost environment accessible
• E2E tests run via Playwright MCP
• All main flows tested
• Accessibility verified
• Evidence screenshots captured
• Bugs documented (if any)
• Final report generated

Important Notes

• Always use browser_snapshot before interacting to understand the current state of the page
• Capture screenshots of ALL bugs found
• If a blocking bug is found, document and report it immediately
• Check the browser console for JavaScript errors with browser_console_messages
• Check API calls with browser_network_requests

QA is only APPROVED when ALL PRD requirements have been verified and are working Use the Playwright MCP for ALL interactions with the application