do-execute-qa

Execute end-to-end QA validation against PRD, Tech Spec, and Tasks using MCP tools.

28|1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-execute-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-execute-qa
Source: https://github.com/fabio-barboza/development-orchestrator/tree/main/skills/do-execute-qa
Command: npx skills add https://github.com/fabio-barboza/development-orchestrator --skill do-execute-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Automates end-to-end QA validation against PRD/Tech Spec and Tasks, including E2E testing via MCP tools, accessibility verification (WCAG 2.2), and visual analysis, and it documents all bugs with screenshots to produce a comprehensive QA report.

Core Features & Use Cases

  • Automated E2E testing and verification against PRD, Tech Spec, and Tasks using browser and backend MCPs.
  • Accessibility validation following WCAG 2.2 checklist with keyboard, focus, and contrast checks.
  • Visual verification across states with structured bug reporting and generated QA artifacts.
  • Automatic bug documentation and generation of a formal QA report for project teams.

Quick Start

Ask the DO framework to run QA on a feature and generate a complete QA report.

Frequently Asked Questions about do-execute-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end QA testing against a PRD and Tech Spec?

Automate end-to-end QA testing by using MCP-based tools to execute browser and backend tests, validating features against PRD, Tech Spec, and Tasks to produce a comprehensive QA report.

Can I validate WCAG 2.2 accessibility compliance during E2E testing?

WCAG 2.2 accessibility validation is performed during E2E testing by checking keyboard navigation, focus management, and contrast ratios, integrating these results into the final QA report.

What's the best way to document bugs with screenshots during visual verification?

Document bugs with screenshots by performing visual verification across states, capturing detailed visual evidence, and generating structured bug reporting artifacts for the project team.

Does this QA process work for both frontend and backend features?

End-to-end QA validation applies to frontend, backend, or full-stack features, executing environment readiness and capability checks to ensure comprehensive coverage across the stack.

What environments do I need to run MCP-based browser and backend tests?

MCP-based browser and backend tests require environment readiness and capability checks to validate the testing setup before executing end-to-end QA validation against project specifications.

Why include accessibility and visual checks in an automated bug report?

Accessibility and visual checks are included in automated bug reporting to capture WCAG 2.2 compliance failures and visual state discrepancies, delivering comprehensive QA documentation with screenshots.