qa

Generates a QA plan and report for the current branch.

8|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yulonghe97/ystack --skill qa-yulonghe97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/yulonghe97/ystack/tree/main/skills/qa
Command: npx skills add https://github.com/yulonghe97/ystack --skill qa-yulonghe97

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA for the ystack agent harness can be slow and error-prone without a structured plan. This skill orchestrates a plan-driven QA workflow, generates a formal QA plan, runs agentic self-tests in parallel, and reports results in QA-REPORT.md. It ensures remediation is explicit and only runs fixes when requested.

Core Features & Use Cases

  • Plan-driven QA workflow: creates and executes a QA plan that covers standards, feature completeness, and agentic tests.
  • Parallel sub-agents: distributes QA tasks across dedicated agents to speed up validation.
  • Reporting and remediation: writes QA-REPORT.md with open issues and supports an optional fix loop when authorized.
  • Use Case: when validating a new branch, run /qa to surface plan gaps and ensure compliance with project standards before go/no-go.

Quick Start

Invoke the QA flow on the current branch by running the /qa command to load standards, plan QA steps, and generate a QA-REPORT.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate plan-driven QA testing for a new branch?

Plan-driven QA testing is automated by loading project standards, scanning for PLAN.md, and classifying feature types to generate a formal QA plan. The workflow validates compliance and writes a QA-REPORT.md.

How do sub-agents speed up agentic testing workflows?

Sub-agents speed up agentic testing workflows by distributing QA tasks across dedicated agents running in parallel. This parallel execution validates feature completeness and standards compliance faster than sequential checks.

Can I automatically run fix loops during an automated QA report generation?

Automated fix loops are not run automatically during QA report generation. The workflow produces QA artifacts and writes open issues to QA-REPORT.md, only executing remediation loops when explicitly authorized by the user.

What is the best way to surface mismatches between user claims and repository changes?

To surface mismatches between user claims and repository changes, the QA workflow identifies the current branch state and QA scope, classifies the feature type, and detects discrepancies against project standards before generating the final report.

Do I need a PLAN.md file to run the agentic-testing workflow?

A PLAN.md file is required to run the agentic-testing workflow. The skill scans for PLAN.md to identify the current branch state and QA scope, using it to classify feature types and structure the validation plan.