Breakdown Test
Turn PRDs, technical breakdowns, and implementation plans into ISTQB-aligned test strategies and GitHub-ready QA task breakdowns before you ship.
Overview
breakdown-test is an agent skill most often used in Ship (also Validate scope, Build pm) that turns feature PRDs and implementation artifacts into ISTQB- and ISO 25010-aligned test strategies and QA task breakdowns for G
Install
npx skills add https://github.com/github/awesome-copilot --skill breakdown-testWhat is this skill?
- Applies ISTQB test process activities from planning through execution and completion
- Maps work to ISO 25010 quality characteristics (functional suitability through portability)
- Produces risk-based testing strategies and explicit entry/exit quality gates
- Consumes PRD, technical breakdown, and implementation plan as required inputs
- Frames deliverables for GitHub project management and traceable QA documentation
- Grounded in ISTQB test process activities and ISO 25010 quality characteristics
- Expects core inputs: Feature PRD, technical breakdown, and implementation plan
Adoption & trust: 8.8k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a PRD and implementation plan but no structured test strategy, risk coverage, or quality gates your agent can execute against.
Who is it for?
Indie builders shipping features on GitHub who already have a PRD or technical breakdown and want professional-grade test planning without hiring a full-time QA lead.
Skip if: Teams that only need a one-off unit test snippet, lack any feature PRD or implementation artifact, or want automated test runners instead of planning documentation.
When should I use this skill?
You have feature artifacts (PRD, technical breakdown, implementation plan) and need comprehensive test strategies and QA documentation for a GitHub-managed project.
What do I get? / Deliverables
You get documented test types, risk-based plans, ISO 25010 validation angles, and GitHub-oriented QA tasks ready to drive implementation and pre-release checks.
- Comprehensive test strategy and task breakdown
- Risk-based testing and quality-gate documentation
- ISO 25010-oriented validation plan for the feature
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because the skill’s output is test planning, quality gates, and validation—not feature design or production ops. Testing subphase matches functional/non-functional test design, risk-based coverage, and ISO 25010 quality validation the prompt mandates.
Where it fits
Derive acceptance-test themes and risk areas while finalizing MVP scope from the PRD.
Split the implementation plan into test design tasks and monitoring hooks before coding sprints start.
Produce functional and non-functional test matrices with quality gates ahead of release.
Attach structural and change-related test expectations to PR review checklists.
How it compares
Use instead of asking the model for a generic test checklist without ISTQB structure, ISO 25010 coverage, or explicit quality gates.
Common Questions / FAQ
Who is breakdown-test for?
Solo and indie builders using GitHub for issue and project tracking who want agent-generated test strategy and QA breakdowns grounded in established quality frameworks.
When should I use breakdown-test?
During Validate when scoping acceptance criteria; during Build pm when an implementation plan lands; and during Ship testing when you need risk-based cases, non-functional coverage, and entry/exit gates before merge or release.
Is breakdown-test safe to install?
It is a documentation and planning prompt without built-in shell or network calls; review the Security Audits panel on this Prism page before adding any skill to your agent workflow.
SKILL.md
READMESKILL.md - Breakdown Test
# Test Planning & Quality Assurance Prompt ## Goal Act as a senior Quality Assurance Engineer and Test Architect with expertise in ISTQB frameworks, ISO 25010 quality standards, and modern testing practices. Your task is to take feature artifacts (PRD, technical breakdown, implementation plan) and generate comprehensive test planning, task breakdown, and quality assurance documentation for GitHub project management. ## Quality Standards Framework ### ISTQB Framework Application - **Test Process Activities**: Planning, monitoring, analysis, design, implementation, execution, completion - **Test Design Techniques**: Black-box, white-box, and experience-based testing approaches - **Test Types**: Functional, non-functional, structural, and change-related testing - **Risk-Based Testing**: Risk assessment and mitigation strategies ### ISO 25010 Quality Model - **Quality Characteristics**: Functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, portability - **Quality Validation**: Measurement and assessment approaches for each characteristic - **Quality Gates**: Entry and exit criteria for quality checkpoints ## Input Requirements Before using this prompt, ensure you have: ### Core Feature Documents 1. **Feature PRD**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}.md` 2. **Technical Breakdown**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md` 3. **Implementation Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md` 4. **GitHub Project Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md` ## Output Format Create comprehensive test planning documentation: 1. **Test Strategy**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-strategy.md` 2. **Test Issues Checklist**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-issues-checklist.md` 3. **Quality Assurance Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/qa-plan.md` ### Test Strategy Structure #### 1. Test Strategy Overview - **Testing Scope**: Features and components to be tested - **Quality Objectives**: Measurable quality goals and success criteria - **Risk Assessment**: Identified risks and mitigation strategies - **Test Approach**: Overall testing methodology and framework application #### 2. ISTQB Framework Implementation ##### Test Design Techniques Selection Create a comprehensive analysis of which ISTQB test design techniques to apply: - **Equivalence Partitioning**: Input domain partitioning strategy - **Boundary Value Analysis**: Edge case identification and testing - **Decision Table Testing**: Complex business rule validation - **State Transition Testing**: System state behavior validation - **Experience-Based Testing**: Exploratory and error guessing approaches ##### Test Types Coverage Matrix Define comprehensive test type coverage: - **Functional Testing**: Feature behavior validation - **Non-Functional Testing**: Performance, usability, security validation - **Structural Testing**: Code coverage and architecture validation - **Change-Related Testing**: Regression and confirmation testing #### 3. ISO 25010 Quality Characteristics Assessment Create a quality characteristics prioritization matrix: - **Functional Suitability**: Completeness, correctness, appropriateness assessment - **Performance Efficiency**: Time behavior, resource utilization, capacity validation - **Compatibility**: Co-existence and interoperability testing - **Usability**: User interface, accessibility, and user experience validation - **Reliability**: Fault tolerance, recoverability, and availability testing - **Security**: Confidentiality, integrity, authentication, and authorization validation - **Maint