One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill qa-plan-imclab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill qa-plan-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents brittle, last-minute testing by turning sprint/feature scope (stories plus referenced GDD acceptance criteria) into a complete, actionable QA plan that developers and QA can execute immediately.

Core Features & Use Cases

  • Sprint/feature/story scope intake: Accepts sprint, feature: system-name, story: path, or prompts for scope when omitted, then enumerates in-scope story files.
  • Spec-driven test classification: Reads each story’s acceptance criteria and classifies it into Logic, Integration, Visual/Feel, UI, or Config/Data with a conservative bias toward Integration when ambiguous.
  • Automated + manual QA coverage: Produces a structured plan including automated test requirements (unit/integration paths), manual verification checklists, smoke-test scope, and playtest sign-off requirements.
  • GDD acceptance-criteria targeting: Loads only the GDD Acceptance Criteria and Formulas sections for each referenced GDD, minimizing noise while ensuring tests track real requirements.
  • Gap detection: Notes missing GDD references without blocking plan generation so the team can address specification coverage gaps.

Quick Start

Ask for a QA plan by running the qa-plan skill with the argument sprint to generate a production QA plan file for the current sprint’s stories.

Frequently Asked Questions about qa-plan

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

FAQPage Schema
How do I generate a QA test plan from sprint stories and GDD acceptance criteria?▼

Generating a QA test plan requires providing sprint or feature scope so the tool can read in-scope story files, extract referenced GDD acceptance criteria, and output a structured document with automated targets and manual checklists.

What types of testing are covered when creating a sprint QA plan?▼

Sprint QA plans cover Logic, Integration, UI, Visual/Feel, and Config/Data testing by classifying story acceptance criteria to produce automated test requirements, manual verification checklists, smoke-test scope, and playtest sign-off guidance.

How are story files classified into test categories during QA planning?▼

Story files are classified into test categories by reading acceptance criteria and Type headers, applying a conservative bias toward Integration testing when classification is ambiguous to ensure broad coverage.

Does the QA plan generator work if a story is missing GDD acceptance criteria references?▼

Yes, the QA plan generator works if GDD references are missing by noting the specification coverage gap without blocking plan generation, allowing the team to address missing requirements later.

Can I generate a QA plan for a single feature or story instead of an entire sprint?▼

Yes, you can generate a QA plan for a single feature or story by passing arguments like feature: system-name or story: path to resolve scope from specific inputs rather than requiring a full sprint.