skills.rest
ultraviollettnympho
ultraviollettnymphoCOMMUNITY
Explore all skills by this author →
GitHub

breakdown-test

Generates test strategies, QA plans, and GitHub issue templates using ISTQB and ISO 25010 frameworks.

1|1|Updated Jan 29, 2026
Search Tags:#quality assurance#test strategy#github issues#playwright#test planning#istqb#iso 25010
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-test-ultraviollettnympho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-test
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/breakdown-test
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-test-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lack a structured, standards-based approach to test planning, resulting in inconsistent coverage, missing quality gates, and poorly defined GitHub test issues. This Skill turns feature artifacts (PRD, technical breakdown, implementation plan) into comprehensive test strategies and QA documentation aligned with ISTQB and ISO 25010. ## Core Features & Use Cases - Test Strategy Generation: Produces a full test strategy document covering ISTQB test design techniques, test type coverage matrices, and risk-based testing approaches. - Quality Assurance Planning: Creates QA plans with ISO 25010 quality characteristics assessment, quality gates, entry/exit criteria, and measurable quality metrics. - GitHub Issue Templates: Provides ready-to-use templates for test strategy issues, Playwright E2E test implementation issues, and quality assurance issues with labels, estimates, and acceptance criteria. - Use Case: After finishing a feature's implementation plan, ask the AI to generate the complete test planning package—test-strategy.md, test-issues-checklist.md, and qa-plan.md—ready to file as GitHub project issues. ## Quick Start Generate a comprehensive test strategy and QA plan for my feature using the PRD and implementation plan in the docs folder.

Frequently Asked Questions about breakdown-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a test strategy from a PRD?▼

Provide the feature PRD, technical breakdown, and implementation plan, then generate a test strategy document covering scope, quality objectives, risk assessment, and ISTQB test design techniques. The output is saved as test-strategy.md in the feature's plan directory.

What is the ISTQB framework in test planning?▼

ISTQB defines test process activities, design techniques like equivalence partitioning and boundary value analysis, and test types including functional, non-functional, structural, and change-related testing. This Skill applies these systematically to each feature's test plan.

How do I write GitHub issues for Playwright end-to-end tests?▼

Use the included Playwright test implementation issue template, which covers test case design, page object model setup, fixtures, visual regression, CI/CD integration, and acceptance criteria with story point estimates of 2-5 points.

What is ISO 25010 and how does it apply to QA?▼

ISO 25010 defines eight software quality characteristics including functional suitability, performance efficiency, usability, security, and reliability. The Skill builds a prioritization matrix and validation approach for each characteristic in the QA plan.

What inputs are required before generating test plans?▼

Four documents are required: the feature PRD, technical breakdown, implementation plan, and GitHub project plan, all located under the docs/ways-of-work/plan directory for the epic and feature. Missing inputs should be created first.

What are the limitations of template-based test planning?▼

Template-driven plans standardize structure but cannot replace domain expertise for novel architectures or highly specialized compliance needs. Estimates and coverage targets still require review by technical leads against historical project data.

Related Skills

Explore More Software Engineering Skills→
GabeujinGabeujin

breakdown-test

Generate test strategies, task breakdowns, and QA plans for GitHub projects.

Community
Advanced
ShadowAUSShadowAUS

iikit-08-taskstoissues

Convert tasks from tasks.md into GitHub Issues with labels and dependencies.

Community
Advanced
jsdfhasuhjsdfhasuh

test-master

Define end-to-end testing workflows with functional, performance, and security validation.

Community
Advanced
tetiannatetianna

exploratory-charter

Formats a feature and risk hypothesis into an exploratory testing charter and findings template.

Community
Basic