Breakdown-Test
Breakdown-Test是一款productivity方向的AI技能,核心价值是Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects,可用于解决开发者在productivity领域的实际问题,帮助用户提升效率、自动化重复任务或优化工作流。
Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.
mkdir -p ./skills/breakdown-test && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/breakdown-test/SKILL.md -o ./skills/breakdown-test/SKILL.md Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# 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
- **Maintainability**: Modularity, reusability, and testability assessment
- **Portability**: Adaptability, installability, and replaceability validation
#### 4. Test Environment and Data Strategy
- **Test En
🎯 Best For
- QA engineers
- Developers writing unit tests
- Developers scaffolding new projects
- Prototype builders
- Claude users
💡 Use Cases
- Generating test cases for edge conditions
- Writing integration test suites
- Bootstrapping React components
- Creating API route handlers
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Breakdown-Test to Your Work
Provide context for your task — paste source material, describe your audience, or share existing work to guide the AI.
- 4
Review and Refine
Edit the AI output for accuracy, tone, and completeness. Add human insight where the AI lacks context.
❓ Frequently Asked Questions
Does this generate test mocks?
Many testing skills include mock generation. Check the install command and skill content for details.
Can I customize the generated output?
Yes — modify the skill's prompt instructions to match your project conventions and coding style.
How do I install Breakdown-Test?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/breakdown-test/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Not testing edge cases
AI tends to generate happy-path tests. Manually review for boundary conditions.
Using generated code without understanding
Understand what generated code does before shipping it to production.
Not reading the full skill
Skills contain important context and edge cases beyond the quick start.