qa-plan

Generates structured QA plans with story classifications and verification guidance.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill qa-plan-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/qa-plan
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill qa-plan-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from planning quality assurance by turning sprint, feature, or story artifacts into a clear test strategy before implementation begins.

Core Features & Use Cases

  • Story Classification: Reads story files and classifies them into the right test type so teams know whether they need contract, smoke, migration, permission, workflow, UI, integration, deployment, or config checks.
  • Evidence-Oriented Planning: Produces concrete automated and manual verification guidance, including smoke scope, required evidence, and sign-off expectations.
  • Repository-Aware QA: Uses CDDs, ADRs, sprint plans, and related docs to ground the test plan in the actual project context.
  • Use Case: A QA lead preparing for a new sprint can generate a structured plan that tells developers exactly what to test, what artifacts to create, and what must be approved before stories are marked complete.

Quick Start

Ask the assistant to generate a QA plan for the current sprint, a specific feature, or a single story from the repository.

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 test strategy from sprint stories and architecture docs?

Story classification for QA planning involves reading story files and assigning them to specific test types like contract, smoke, migration, permission, workflow, UI, integration, deployment, or config checks. This classification determines what evidence and verification scopes are required for sign-off.

How do I structure smoke checks and automated verification scope for a new feature?

Structuring smoke checks and automated verification scope requires mapping classified stories to concrete test artifacts and sign-off criteria. The Skill uses repository context like ADRs and sprint plans to ground the scope in actual project requirements.

Can I use repository artifacts like ADRs and CDDs to plan contract tests?

Yes, you can use repository artifacts to plan contract tests because the Skill reads ADRs, CDDs, and related architecture docs. This repository-aware approach grounds the test plan in actual project context to ensure accurate verification guidance.

What is the best way to map story files to required test evidence before implementation?

The best way to map story files to required test evidence is to classify them by test type and generate an evidence-oriented plan. This defines exactly what artifacts developers must create and what must be approved before stories are marked complete.

Do I need sprint context and story files in the repository to define QA sign-off criteria?

You need sprint context and story files in the repository to define accurate QA sign-off criteria. The Skill requires reading these artifacts alongside CDDs and architecture docs to produce grounded test guidance and clear approval expectations.