qa-guide

Generate a structured QA test guide from task-plan documents.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/paycrux/ai-skills --skill qa-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-guide
Source: https://github.com/paycrux/ai-skills/tree/main/.claude/skills/qa-guide
Command: npx skills add https://github.com/paycrux/ai-skills --skill qa-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read task-plan documentation and produce a structured QA test guide in markdown that the QA team can use immediately.

Core Features & Use Cases

  • Automatic consolidation of five plan files (README.md, spec.md, tasks.md, progress.md, findings.md) into a single QA guide
  • Template-based output saved to docs/<task-folder-name>/qa-guide.md
  • Scenario writing rules and Korean language template to ensure consistent, actionable test cases

Quick Start

Invoke /qa-guide to generate a QA test guide from the latest in-progress or completed task-plan folder.

Frequently Asked Questions about qa-guide

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

FAQPage Schema
How do I generate a QA test guide from task plan documentation?

Generate a QA test guide by reading five task-plan files (README.md, spec.md, tasks.md, progress.md, findings.md) and consolidating them into a single markdown file formatted with scenario writing rules for immediate testing.

What task-plan files do I need to prepare before auto-generating a QA guide?

You need five markdown files in your docs folder: README.md, spec.md, tasks.md, progress.md, and findings.md, which the tool reads to extract requirements, implementation status, and issue tracking data for the test guide.

Can I automatically detect in-progress or completed task plans for QA documentation?

Yes, auto-detection scans folders under docs/ to locate the latest in-progress or completed task-plan folder, reads its five markdown files, and outputs the structured qa-guide.md directly into that task folder.

What's the best way to structure test cases from spec and progress markdown files?

Structure test cases by applying template-based scenario writing rules to the consolidated spec.md and progress.md data, ensuring consistent, actionable test cases formatted in a standardized markdown output.

Does the generated QA guide support Korean language test case templates?

Yes, the generated QA guide supports Korean language templates alongside scenario writing rules to ensure consistent, actionable test cases tailored for QA teams requiring localized documentation.

Why is my QA guide not generating from the docs task folder?

Generation fails if the expected five files (README.md, spec.md, tasks.md, progress.md, findings.md) are missing from the task folder, or if no in-progress or completed plan is detected under the docs/ directory.