breakdown-test Skill for Claude: Test Plans and QA Issues

Makes Claude write a test strategy, a test issue checklist and a QA plan for a feature, based on ISTQB and ISO 25010.

Installs: 9.3K; on skills.sh
Stars: 40.7K; on GitHub
Updated: Oct 2026; last repo commit

This skill makes Claude act as a QA engineer and test architect. It reads your feature PRD, technical breakdown, implementation plan and GitHub project plan (the PRD at /docs/ways-of-work/plan/{epic-name}/{feature-name}.md, the rest in /docs/ways-of-work/plan/{epic-name}/{feature-name}/), then writes three files there: test-strategy.md, test-issues-checklist.md and qa-plan.md.

The work is framed by ISTQB test design techniques and the ISO 25010 quality model. It includes issue templates for the test strategy, Playwright test implementation and quality assurance. It bundles no scripts, and SKILL.md names no API key. The input documents must exist first.

Good for

QA engineers and test leads planning coverage for a feature
Teams that track test work as GitHub issues
Developers who already have a project plan and want matching test tasks

Install breakdown-test

Claude Code

Copy this prompt.

Install the breakdown-test skill in Claude Code. Run this command:

npx skills add https://github.com/github/awesome-copilot --skill breakdown-test

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.

Sections in SKILL.md

Goal
Quality Standards Framework
ISTQB Framework Application
ISO 25010 Quality Model
Input Requirements
Core Feature Documents
Output Format
Test Strategy Structure
Test Issues Checklist
Task Level Breakdown
Quality Assurance Plan
GitHub Issue Templates for Testing
Test Strategy Issue Template
Test Strategy Overview
ISTQB Framework Application
ISO 25010 Quality Characteristics

Key facts

Listed in: github/awesome-copilot (the README says its contents come from third-party developers)
Repo: github/awesome-copilot
Installs on skills.sh: 9,269 (Nov 2, 2026)
GitHub stars: 40,666 (Nov 2, 2026)
License: MIT (repo license)
Last repo commit: Oct 30, 2026
What installs: 1 file: SKILL.md, no scripts
Writes: test-strategy.md, test-issues-checklist.md and qa-plan.md in /docs/ways-of-work/plan/{epic-name}/{feature-name}/

What it includes

Four input docs: PRD, technical breakdown, implementation plan and project plan
Four markdown files per feature. The project-plan.md is the file that breakdown-plan writes.
Files · Inputs it expects
Test strategy with ISTQB techniques, test types, ISO 25010 review and environment plan
Four parts: strategy overview, ISTQB framework implementation, ISO 25010 quality characteristics assessment, and test environment and data strategy.
Write · test-strategy.md
Checklist of test-level issues, test types, dependencies and coverage targets
Covers unit, integration, end-to-end (Playwright), performance, security, accessibility and regression issues.
Write · test-issues-checklist.md
Quality gates, issue standards, labels, dependency checks and estimate reviews
Defines entry and exit checkpoints for quality and the standards each GitHub test issue must meet.
Write · qa-plan.md
Three templates: test strategy, Playwright test implementation, quality assurance
Each carries scope, acceptance criteria, labels and an estimate.
Issue templates

From the official docs

Questions

What does breakdown-test do?

It makes Claude plan the testing for a feature: a test strategy, a checklist of test issues and a QA plan. It applies ISTQB test design techniques and the ISO 25010 quality characteristics.

How do I install it in Claude Code?

Use the install box at the top of the page. No plugin in the awesome-copilot repo lists this skill, so the box installs the skill folder on its own.

What do I need before I run it?

Four markdown files: the feature PRD at /docs/ways-of-work/plan/{epic-name}/{feature-name}.md, and technical-breakdown.md, implementation-plan.md and project-plan.md in /docs/ways-of-work/plan/{epic-name}/{feature-name}/.

How does it relate to breakdown-plan?

breakdown-plan writes the project-plan.md that this skill reads as an input. Run breakdown-plan first, then breakdown-test.

Does it write the tests themselves?

It plans them. Its three output files are documents, and its issue templates include a Playwright test implementation template with test cases to implement. SKILL.md does not ask Claude to write test code files.

Is it safe?

It bundles no scripts, only a SKILL.md. It writes three markdown files in /docs/ways-of-work/plan/{epic-name}/{feature-name}/, so work in a repository where that is fine. The awesome-copilot README says its items come from third-party developers and asks you to inspect them before installing.

Information

updated Nov 2, 2026

Repository: github/awesome-copilot
Folder: skills/breakdown-test

github/awesome-copilot skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3

SKILL.md · github.com
awesome-copilot README · github.com
breakdown-plan SKILL.md · github.com