skills.rest
hoonsubin
hoonsubinCOMMUNITY
Explore all skills by this author →
Website𝕏@hoonsubinGitHub

breakdown-test

Generates test strategies, QA plans, and test issue breakdowns for GitHub projects.

Updated Apr 22, 2026
Search Tags:#quality assurance#test strategy#github issues#playwright#test planning#istqb#iso 25010
One-click install
npx skills add https://github.com/hoonsubin/scrum-master-mcp-server --skill breakdown-test-hoonsubin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-test
Source: https://github.com/hoonsubin/scrum-master-mcp-server/tree/main/.roo/skills/breakdown-test
Command: npx skills add https://github.com/hoonsubin/scrum-master-mcp-server --skill breakdown-test-hoonsubin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship features without a structured quality plan, leaving test coverage, risk assessment, and QA task estimation to ad-hoc decisions. This Skill turns feature planning artifacts into comprehensive test strategies and actionable GitHub test issues aligned with ISTQB and ISO 25010 standards. ## Core Features & Use Cases - Test Strategy Generation: Produces a test strategy document covering ISTQB test design techniques, test type coverage matrices, and risk-based testing approaches. - QA Planning & Quality Gates: Creates quality assurance plans with entry/exit criteria, ISO 25010 quality characteristic assessments, and measurable quality metrics. - GitHub Test Issue Breakdown: Outputs ready-to-use issue templates for test strategy, Playwright E2E tests, and QA validation, including labels, estimates, and dependency tracking. - Use Case: After finishing a feature PRD and implementation plan, ask the agent to produce the full test planning package: a test-strategy.md, a test-issues-checklist.md, and a qa-plan.md under the feature's docs folder, plus GitHub issues for each test level. ## Quick Start Generate a complete test strategy, QA plan, and GitHub test issue breakdown for the feature documented in docs/ways-of-work/plan using ISTQB and ISO 25010 standards.

Frequently Asked Questions about breakdown-test

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

FAQPage Schema
How do I create a test strategy from a feature PRD?▼

Provide the feature PRD, technical breakdown, and implementation plan documents, then the Skill generates a test-strategy.md covering scope, quality objectives, risk assessment, ISTQB test design techniques, and test type coverage. Output is written to the feature's docs folder.

What ISTQB test design techniques does this test planning cover?▼

It covers equivalence partitioning, boundary value analysis, decision table testing, state transition testing, and experience-based testing. The generated strategy selects which techniques apply and maps them to functional, non-functional, structural, and change-related test types.

How are GitHub test issues structured and estimated?▼

The Skill provides templates for test strategy, Playwright E2E, and QA issues with labels like unit-test, e2e-test, and test-critical. Estimation guidelines suggest 0.5-1 points per unit test, 2-3 per E2E workflow, and 3-5 per performance requirement.

Does this support ISO 25010 quality characteristics?▼

Yes, the QA plan assesses all eight ISO 25010 characteristics including functional suitability, performance efficiency, security, and usability. Each characteristic gets a priority rating and a validation approach with quality gates and exit criteria.

What inputs are required before generating test plans?▼

Four documents are required: the feature PRD, technical breakdown, implementation plan, and GitHub project plan, all located under docs/ways-of-work/plan/{epic-name}/{feature-name}/. Missing inputs mean the strategy cannot be grounded in actual feature scope.

When should I not use this test planning approach?▼

It is heavyweight for trivial changes or prototypes without formal PRDs, since it expects structured planning documents as input. Small bug fixes or spikes are better served by lightweight checklists rather than full ISTQB and ISO 25010 documentation.

Related Skills

Explore More Software Engineering Skills→
nashirabbashnashirabbash

breakdown-test

Generate test strategies, QA plans, and issue checklists from feature artifacts for GitHub projects.

Community
Advanced
MichaelSolatiMichaelSolati

bug-triage

Classify game bugs by severity and priority, assign sprints, and generate triage reports.

Community
Advanced
MDLDev-siteMDLDev-site

qa-automation-engineer

Automates QA testing from planning to execution with quality gates.

Official
Advanced
epologeeepologee
3

testing-philosophy

Enforce test-driven development with failing specs before implementation.

Community
Intermediate