qa-orchestrate

Orchestrates tester, security, and report agents into one automated QA workflow.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-orchestrate-karentenorio963
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-orchestrate
Source: https://github.com/KarenTenorio963/curso-mcp-karentenorio/tree/main/entregas/s4/mi-proyecto-speckit/.agents/skills/qa-orchestrate
Command: npx skills add https://github.com/KarenTenorio963/curso-mcp-karentenorio --skill qa-orchestrate-karentenorio963

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running quality assurance across testing, security review, and reporting normally requires manually invoking each agent and confirming every step, which fragments the workflow and slows down delivery. ## Core Features & Use Cases - Sequential Agent Orchestration: Invokes tester-agent, security-agent, and report-agent in a fixed order, waiting for each to finish before starting the next. - Spec Kit Validation: Checks that a specs/*/spec.md file exists before starting, and stops with a clear instruction to run Spec Kit first if it is missing. - Unattended Execution: Runs the full pipeline without asking for confirmation between phases, then presents a final verdict with a one-line summary per agent. - Use Case: After generating a feature specification with Spec Kit, trigger this Skill to automatically run tests, perform a security review, and produce a consolidated quality report in a single pass. ## Quick Start Run the full QA pipeline on my current Spec Kit specification and give me the final verdict.

Frequently Asked Questions about qa-orchestrate

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

FAQPage Schema
How do I run automated QA on a Spec Kit specification?▼

Invoke the qa-orchestrate skill after generating your specification with Spec Kit. It verifies the spec.md file exists, then runs the tester, security, and report agents in sequence and returns a final verdict.

What agents does the QA orchestration workflow run?▼

The workflow runs three agents in fixed order: tester-agent for testing, security-agent for security review, and report-agent for the consolidated report. Each agent's detailed task lives in its own agent.md file.

Why does the QA pipeline stop before running any agents?▼

The pipeline stops when no specs/*/spec.md file exists in the project. Run Spec Kit first to generate the specification, then re-invoke the orchestration skill.

Does the QA workflow ask for confirmation between phases?▼

No, it runs automatically from start to finish without pausing between agents. If the environment requests approval to invoke each agent, approve the permission and the flow continues.

What output does the QA orchestration produce at the end?▼

It presents a final verdict to the user along with a one-line summary of what each agent did during the run. The detailed artifacts come from the individual tester, security, and report agents.