qa-plan

Name: qa-plan
Availability: InStock
Author: lekay

Parse story files and GDDs to generate structured QA plans in Markdown.

Updated May 24, 2026

Search Tags:#code review #test automation #software testing #sprint management #qa planning

Ready to run

npx skills add https://github.com/LeKay/ai-game --skill qa-plan-lekay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-plan
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/qa-plan
Command: npx skills add https://github.com/LeKay/ai-game --skill qa-plan-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the creation of QA test plans by automatically generating a detailed structure for automated tests, manual verification steps, smoke test scopes, and playtest requirements.

Core Features & Use Cases

Automated QA Plan Generation: Based on story files and GDDs, classifies stories, identifies automated tests, and outlines manual test cases.
Scope Determination: Allows specification of scope for a sprint, feature, or individual story.
Structured Output: Delivers a comprehensive, actionable QA plan in Markdown format.

Quick Start

Generate a QA plan for the current sprint by running the qa-plan skill with no arguments.

Frequently Asked Questions about qa-plan

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

FAQPage Schema

How do I automate QA planning for a software sprint?▼

Automate QA planning by parsing story files and GDDs to classify story types and outline automated and manual test requirements. This generates a structured QA plan covering smoke tests, playtests, and verification steps for your sprint.

What is the best way to generate a structured test plan from story files?▼

Generating a structured test plan from story files involves classifying story types and extracting automated test scopes and manual verification steps. This approach delivers a comprehensive, actionable QA plan formatted in Markdown.

Can I scope QA test plans to a single feature instead of an entire sprint?▼

Yes, you can scope QA test plans to a single feature, an individual story, or an entire sprint. Specifying the scope allows you to tailor the generated automated tests and manual verification steps to the exact target area.

Do I need GDDs and system documentation to create automated test requirements?▼

Yes, you need GDDs and system documentation to create automated test requirements, as these documents provide the necessary context for classifying story types and accurately outlining both automated and manual test cases.

How does story type classification improve software testing plans?▼

Story type classification improves software testing plans by categorizing requirements from story files, which allows the system to accurately distinguish between necessary automated tests, manual test cases, and playtest requirements for each feature.

What format does the generated QA plan use for test automation and manual verification?▼

The generated QA plan uses a Markdown format to outline test automation and manual verification steps. This structured output ensures the plan is comprehensive, readable, and actionable for sprint management and software testing.