Skip to content
EN
العربيةEnglishEspañol
github/awesome-copilot

Test Planning and Quality Assurance for GitHub Projects Following ISTQB and ISO 25010 Standards

GitHub CopilotClaude CodeCursorDevin / WindsurfGemini CLIOpenAI Codex

About this skill

Text-based instructions that have the agent act as a quality assurance engineer and test architect. The agent reads the feature documentation: the Product Requirements Document (PRD), the technical breakdown, the implementation plan, and the project plan. It then prepares three documents: a test strategy, a test task checklist, and a quality assurance plan. These documents are based on the ISTQB framework and the ISO 25010 quality model. They include GitHub issue templates, suggested labels, story point estimates, and entry and exit criteria for quality gates.
Start here

How do you use this skill?

1. Prepare the feature documentation at the expected paths: `/docs/ways-of-work/plan/{epic-name}/{feature-name}.md`, as well as `technical-breakdown.md`, `implementation-plan.md`, and `project-plan.md` inside the feature folder. 2. Ask the agent to prepare the test plan. Example user request: "Prepare a comprehensive test strategy, a test issues checklist, and a quality assurance plan for the login feature within the account management epic, based on the documents in the plan folder." 3. The agent analyzes the documents and selects suitable test design techniques, such as equivalence partitioning and boundary value analysis. It then prioritizes quality characteristics according to ISO 25010. 4. The agent creates the files `test-strategy.md`, `test-issues-checklist.md`, and `qa-plan.md` in the feature folder. These files include ready-to-use issue templates, including a template for Playwright tests. 5. Review the estimates and suggested labels, such as `unit-test`, `e2e-test`, and `test-critical`, as well as the quality gate criteria. Adjust them to suit your team before creating the issues manually in GitHub.

Requirements and limitations

- All four feature documents must already exist in the `/docs/ways-of-work/plan/` folder structure for the outputs to be accurate. - The agent needs permission to read and write files within the repository. - The skill consists of text instructions only and includes no scripts or tools. It does not create GitHub issues automatically and does not run any tests. Using the templates in GitHub requires an account and a project there, and the user creates the issues themselves. - References to Playwright and coverage targets, such as line coverage above 80%, are planning recommendations only and are not included tools. - Output quality depends on the completeness of the input documents and requires human review. - License: MIT.

Installation by agent

Download and extract the ZIP. It contains the folder breakdown-test and the file SKILL.md with the original attachments and license.

GitHub Copilot
  1. Create this path inside your project if it does not exist:.github/skills/
  2. Copy the entire extracted skill folder to this path:.github/skills/breakdown-test/SKILL.md
  3. Open the project in your agent or refresh the skills list and look for breakdown-test.
  4. Request the task shown above and select the skill. Grant only necessary permissions.
Guide GitHub Copilot official documentation ↗
Claude Code
  1. Create this path inside your project if it does not exist:.claude/skills/
  2. Copy the entire extracted skill folder to this path:.claude/skills/breakdown-test/SKILL.md
  3. Open the project in your agent or refresh the skills list and look for breakdown-test.
  4. Request the task shown above and select the skill. Grant only necessary permissions.
Guide Claude Code official documentation ↗
Cursor
  1. Create this path inside your project if it does not exist:.cursor/skills/
  2. Copy the entire extracted skill folder to this path:.cursor/skills/breakdown-test/SKILL.md
  3. Open the project in your agent or refresh the skills list and look for breakdown-test.
  4. Request the task shown above and select the skill. Grant only necessary permissions.
Guide Cursor official documentation ↗
Devin / Windsurf
  1. Create this path inside your project if it does not exist:.devin/skills/
  2. Copy the entire extracted skill folder to this path:.devin/skills/breakdown-test/SKILL.md
  3. Open the project in your agent or refresh the skills list and look for breakdown-test.
  4. Request the task shown above and select the skill. Grant only necessary permissions.
Guide Devin / Windsurf official documentation ↗
Gemini CLI
  1. Create this path inside your project if it does not exist:.gemini/skills/
  2. Copy the entire extracted skill folder to this path:.gemini/skills/breakdown-test/SKILL.md
  3. Open the project in your agent or refresh the skills list and look for breakdown-test.
  4. Request the task shown above and select the skill. Grant only necessary permissions.
Guide Gemini CLI official documentation ↗
OpenAI Codex
  1. Create this path inside your project if it does not exist:.agents/skills/
  2. Copy the entire extracted skill folder to this path:.agents/skills/breakdown-test/SKILL.md
  3. Open the project in your agent or refresh the skills list and look for breakdown-test.
  4. Request the task shown above and select the skill. Grant only necessary permissions.
Guide OpenAI Codex official documentation ↗

Original files retain their language to preserve tool names and paths. Compatibility is classified by review, not runtime testing on every agent version.