Official agent skill

Breakdown Test

by github in github/awesome-copilot

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

OfficialMITAuto-check passedTesting & QA

Install Breakdown Test

skills CLI
$ npx skills add github/awesome-copilot --skill breakdown-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot breakdown-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/breakdown-test .claude/skills/breakdown-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
breakdown-test
GitHub stars
40k
Used in
1 other repo
Token cost
~3.7k tokens
SKILL.md length
1,123 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 4 steps: Test Strategy Overview → ISTQB Framework Implementation → ISO 25010 Quality Characteristics… → …
  • Tasks that involve Test strategy
  • SKILL.md covers Goal, Quality Standards Framework, Input Requirements and Output Format, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Breakdown Test is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test strategy, QA and bug reports and Task breakdown. It works with GitHub. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Tasks that involve Test strategy
  • Tasks that involve QA and bug reports
  • Tasks that involve Task breakdown

Example prompts

  • “/breakdown-test”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Test Strategy Overview
  2. ISTQB Framework Implementation
  3. ISO 25010 Quality Characteristics Assessment
  4. Test Environment and Data Strategy

What it can do on your machine

Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Breakdown Test loads about 3.7k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 1,123 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 1,123 words, ~3,741 tokens.

Download SKILL.mdSave it as .claude/skills/breakdown-test/SKILL.md (or your agent's skills folder).
name
breakdown-test
description
Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.

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 Environment Requirements: Hardware, software, and network configurations
  • Test Data Management: Data preparation, privacy, and maintenance strategies
  • Tool Selection: Testing tools, frameworks, and automation platforms
  • CI/CD Integration: Continuous testing pipeline integration
Test Issues Checklist
Test Level Issues Creation
  • Test Strategy Issue: Overall testing approach and quality validation plan
  • Unit Test Issues: Component-level testing for each implementation task
  • Integration Test Issues: Interface and interaction testing between components
  • End-to-End Test Issues: Complete user workflow validation using Playwright
  • Performance Test Issues: Non-functional requirement validation
  • Security Test Issues: Security requirement and vulnerability testing
  • Accessibility Test Issues: WCAG compliance and inclusive design validation
  • Regression Test Issues: Change impact and existing functionality preservation
Test Types Identification and Prioritization
  • Functional Testing Priority: Critical user paths and core business logic
  • Non-Functional Testing Priority: Performance, security, and usability requirements
  • Structural Testing Priority: Code coverage targets and architecture validation
  • Change-Related Testing Priority: Risk-based regression testing scope
Test Dependencies Documentation
  • Implementation Dependencies: Tests blocked by specific development tasks
  • Environment Dependencies: Test environment and data requirements
  • Tool Dependencies: Testing framework and automation tool setup
  • Cross-Team Dependencies: Dependencies on external systems or teams
Test Coverage Targets and Metrics
  • Code Coverage Targets: >80% line coverage, >90% branch coverage for critical paths
  • Functional Coverage Targets: 100% acceptance criteria validation
  • Risk Coverage Targets: 100% high-risk scenario validation
  • Quality Characteristics Coverage: Validation approach for each ISO 25010 characteristic
Task Level Breakdown
Implementation Task Creation and Estimation
  • Test Implementation Tasks: Detailed test case development and automation tasks
  • Test Environment Setup Tasks: Infrastructure and configuration tasks
  • Test Data Preparation Tasks: Data generation and management tasks
  • Test Automation Framework Tasks: Tool setup and framework development
Task Estimation Guidelines
  • Unit Test Tasks: 0.5-1 story point per component
  • Integration Test Tasks: 1-2 story points per interface
  • E2E Test Tasks: 2-3 story points per user workflow
  • Performance Test Tasks: 3-5 story points per performance requirement
  • Security Test Tasks: 2-4 story points per security requirement
Show full SKILL.md (435 more words)Show less
Task Dependencies and Sequencing
  • Sequential Dependencies: Tests that must be implemented in specific order
  • Parallel Development: Tests that can be developed simultaneously
  • Critical Path Identification: Testing tasks on the critical path to delivery
  • Resource Allocation: Task assignment based on team skills and capacity
Task Assignment Strategy
  • Skill-Based Assignment: Matching tasks to team member expertise
  • Capacity Planning: Balancing workload across team members
  • Knowledge Transfer: Pairing junior and senior team members
  • Cross-Training Opportunities: Skill development through task assignment
Quality Assurance Plan
Quality Gates and Checkpoints

Create comprehensive quality validation checkpoints:

  • Entry Criteria: Requirements for beginning each testing phase
  • Exit Criteria: Quality standards required for phase completion
  • Quality Metrics: Measurable indicators of quality achievement
  • Escalation Procedures: Process for addressing quality failures
GitHub Issue Quality Standards
  • Template Compliance: All test issues follow standardized templates
  • Required Field Completion: Mandatory fields populated with accurate information
  • Label Consistency: Standardized labeling across all test work items
  • Priority Assignment: Risk-based priority assignment using defined criteria
  • Value Assessment: Business value and quality impact assessment
Labeling and Prioritization Standards
  • Test Type Labels: unit-test, integration-test, e2e-test, performance-test, security-test
  • Quality Labels: quality-gate, iso25010, istqb-technique, risk-based
  • Priority Labels: test-critical, test-high, test-medium, test-low
  • Component Labels: frontend-test, backend-test, api-test, database-test
Dependency Validation and Management
  • Circular Dependency Detection: Validation to prevent blocking relationships
  • Critical Path Analysis: Identification of testing dependencies on delivery timeline
  • Risk Assessment: Impact analysis of dependency delays on quality validation
  • Mitigation Strategies: Alternative approaches for blocked testing activities
Estimation Accuracy and Review
  • Historical Data Analysis: Using past project data for estimation accuracy
  • Technical Lead Review: Expert validation of test complexity estimates
  • Risk Buffer Allocation: Additional time allocation for high-uncertainty tasks
  • Estimate Refinement: Iterative improvement of estimation accuracy

GitHub Issue Templates for Testing

Test Strategy Issue Template
markdown
# Test Strategy: {Feature Name}

## Test Strategy Overview

{Summary of testing approach based on ISTQB and ISO 25010}

## ISTQB Framework Application

**Test Design Techniques Used:**
- [ ] Equivalence Partitioning
- [ ] Boundary Value Analysis
- [ ] Decision Table Testing
- [ ] State Transition Testing
- [ ] Experience-Based Testing

**Test Types Coverage:**
- [ ] Functional Testing
- [ ] Non-Functional Testing
- [ ] Structural Testing
- [ ] Change-Related Testing (Regression)

## ISO 25010 Quality Characteristics

**Priority Assessment:**
- [ ] Functional Suitability: {Critical/High/Medium/Low}
- [ ] Performance Efficiency: {Critical/High/Medium/Low}
- [ ] Compatibility: {Critical/High/Medium/Low}
- [ ] Usability: {Critical/High/Medium/Low}
- [ ] Reliability: {Critical/High/Medium/Low}
- [ ] Security: {Critical/High/Medium/Low}
- [ ] Maintainability: {Critical/High/Medium/Low}
- [ ] Portability: {Critical/High/Medium/Low}

## Quality Gates
- [ ] Entry criteria defined
- [ ] Exit criteria established
- [ ] Quality thresholds documented

## Labels
`test-strategy`, `istqb`, `iso25010`, `quality-gates`

## Estimate
{Strategic planning effort: 2-3 story points}
Playwright Test Implementation Issue Template
markdown
# Playwright Tests: {Story/Component Name}

## Test Implementation Scope
{Specific user story or component being tested}

## ISTQB Test Case Design
**Test Design Technique**: {Selected ISTQB technique}
**Test Type**: {Functional/Non-Functional/Structural/Change-Related}

## Test Cases to Implement
**Functional Tests:**
- [ ] Happy path scenarios
- [ ] Error handling validation
- [ ] Boundary value testing
- [ ] Input validation testing

**Non-Functional Tests:**
- [ ] Performance testing (response time < {threshold})
- [ ] Accessibility testing (WCAG compliance)
- [ ] Cross-browser compatibility
- [ ] Mobile responsiveness

## Playwright Implementation Tasks
- [ ] Page Object Model development
- [ ] Test fixture setup
- [ ] Test data management
- [ ] Test case implementation
- [ ] Visual regression tests
- [ ] CI/CD integration

## Acceptance Criteria
- [ ] All test cases pass
- [ ] Code coverage targets met (>80%)
- [ ] Performance thresholds validated
- [ ] Accessibility standards verified

## Labels
`playwright`, `e2e-test`, `quality-validation`

## Estimate
{Test implementation effort: 2-5 story points}
Quality Assurance Issue Template
markdown
# Quality Assurance: {Feature Name}

## Quality Validation Scope
{Overall quality validation for feature/epic}

## ISO 25010 Quality Assessment
**Quality Characteristics Validation:**
- [ ] Functional Suitability: Completeness, correctness, appropriateness
- [ ] Performance Efficiency: Time behavior, resource utilization, capacity
- [ ] Usability: Interface aesthetics, accessibility, learnability, operability
- [ ] Security: Confidentiality, integrity, authentication, authorization
- [ ] Reliability: Fault tolerance, recovery, availability
- [ ] Compatibility: Browser, device, integration compatibility
- [ ] Maintainability: Code quality, modularity, testability
- [ ] Portability: Environment adaptability, installation procedures

## Quality Gates Validation
**Entry Criteria:**
- [ ] All implementation tasks completed
- [ ] Unit tests passing
- [ ] Code review approved

**Exit Criteria:**
- [ ] All test types completed with >95% pass rate
- [ ] No critical/high severity defects
- [ ] Performance benchmarks met
- [ ] Security validation passed

## Quality Metrics
- [ ] Test coverage: {target}%
- [ ] Defect density: <{threshold} defects/KLOC
- [ ] Performance: Response time <{threshold}ms
- [ ] Accessibility: WCAG {level} compliance
- [ ] Security: Zero critical vulnerabilities

## Labels
`quality-assurance`, `iso25010`, `quality-gates`

## Estimate
{Quality validation effort: 3-5 story points}

Success Metrics

Test Coverage Metrics
  • Code Coverage: >80% line coverage, >90% branch coverage for critical paths
  • Functional Coverage: 100% acceptance criteria validation
  • Risk Coverage: 100% high-risk scenario testing
  • Quality Characteristics Coverage: Validation for all applicable ISO 25010 characteristics
Quality Validation Metrics
  • Defect Detection Rate: >95% of defects found before production
  • Test Execution Efficiency: >90% test automation coverage
  • Quality Gate Compliance: 100% quality gates passed before release
  • Risk Mitigation: 100% identified risks addressed with mitigation strategies
Process Efficiency Metrics
  • Test Planning Time: <2 hours to create comprehensive test strategy
  • Test Implementation Speed: <1 day per story point of test development
  • Quality Feedback Time: <2 hours from test completion to quality assessment
  • Documentation Completeness: 100% test issues have complete template information

This comprehensive test planning approach ensures thorough quality validation aligned with industry standards while maintaining efficient project management and clear accountability for all testing activities.

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/breakdown-test of github/awesome-copilot.

Open the folder on GitHubat commit 727ff2e

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Breakdown Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Breakdown Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Breakdown Test this skillgithub/awesome-copilot40k1 repos~3.7kAutomated safety check: PassMIT
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness1.7k—~1.6kAutomated safety check: PassMIT
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Senior QAnicepkg/auto-company1923 repos~1.1kAutomated safety check: NotesNone
Create GitHub IssueNVIDIA/OpenShell15k—~1.7kAutomated safety check: PassApache-2.0
Triage IssuesClickHouse/clickhouse-java1.6k—~904Automated safety check: PassApache-2.0

Similar skills

  • Weavebench Cua Reproduce

    AMAP-ML/LongHorizon-Harness

    Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.

    1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed
  • Senior QA

    nicepkg/auto-company

    Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications.

    192 GitHub starsUsed in 3 repos~1.1k tokens
    Testing & QAAuto-check: notes
  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Triage Issues

    ClickHouse/clickhouse-java

    Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.

    1.6k GitHub stars~904 tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Gentle AI Issue Creation

    Gentleman-Programming/gentle-shell

    Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.

    1.2k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo
  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Breakdown Test

What does Breakdown Test do?

Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects. Breakdown Test is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.

When should I use Breakdown Test?

Breakdown Test fits situations like: tasks that involve Test strategy; tasks that involve QA and bug reports; tasks that involve Task breakdown.

How do I install Breakdown Test in Claude Code?

Run `npx skills add github/awesome-copilot --skill breakdown-test -a claude-code`. Or copy the skill folder (skills/breakdown-test in github/awesome-copilot) into .claude/skills/breakdown-test in your project. Claude Code loads it when a task matches its description.

How do I install Breakdown Test in Codex?

Run `npx skills add github/awesome-copilot --skill breakdown-test -a codex`. Or copy the skill folder (skills/breakdown-test in github/awesome-copilot) into .agents/skills/breakdown-test in your project. Codex loads it when a task matches its description.

Can I use Breakdown Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill breakdown-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/breakdown-test, .gemini/skills/breakdown-test, .github/skills/breakdown-test and .opencode/skills/breakdown-test in your project.

What does Breakdown Test need to run?

SKILL.md names no scripts, command-line tools or credentials: Breakdown Test is instructions for the agent only.

Does Breakdown Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Breakdown Test safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Breakdown Test use?

Breakdown Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Breakdown Test use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Breakdown Test?

Skills that share tags, products or a category with Breakdown Test: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Senior QA (nicepkg/auto-company, 192 stars) and Create GitHub Issue (NVIDIA/OpenShell, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Breakdown Test?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.