Mmcp.market

breakdown-test skill

by github·github/awesome-copilot·39k stars·MIT

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

A100/100content scan

Is the breakdown-test skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the breakdown-test skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/github/awesome-copilot.git /tmp/awesome-copilot
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-copilot/skills/breakdown-test ~/.claude/skills/breakdown-test
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

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

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

More skills from github/awesome-copilot

  • Aacquire-codebase-knowledgeUse this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
  • Aacreadiness-assessRun the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
  • Aacreadiness-generate-instructionsGenerate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
  • Aacreadiness-policyHelp the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
  • Aad-campaign-analyzerUse this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign planning or creative generation without performance data.
  • Aadd-educational-commentsAdd educational comments to the file specified, or prompt asking for file to comment if one is not provided.
  • Aadobe-illustrator-scriptingWrite, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model, coordinate system, measurement units, export workflows, and scripting best practices.
  • Aagent-architectureDesign AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.
  • Aagent-governancePatterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
  • Aagent-owasp-complianceCheck any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"
  • Aagent-skill-stackFind, evaluate, and assemble the smallest compatible set of AI Agent Skills for an end-to-end natural-language goal. Use when a user wants Skills for a multi-step workflow, asks which Skills fit a project, needs an installed-Skill audit or conflict check, has low Skill recall, wants indirect helpers such as humanizers or compliance checks, or wants a project-specific Skill Stack with controlled installation. Search local Skills, registries, GitHub, and OpenCLI; compare adoption, verified fit, safety, and overlap. Do not use for locating one known or common Skill; use the generic find-skills workflow.
  • Aagent-supply-chainVerify supply chain integrity for AI agent plugins, tools, and dependencies. Use this skill when: - Generating SHA-256 integrity manifests for agent plugins or tool packages - Verifying that installed plugins match their published manifests - Detecting tampered, modified, or untracked files in agent tool directories - Auditing dependency pinning and version policies for agent components - Building provenance chains for agent plugin promotion (dev → staging → production) - Any request like "verify plugin integrity", "generate manifest", "check supply chain", or "sign this plugin"

All agent skills → · MCP servers