test-management

Orchestrate QA team capacity planning, execution monitoring, and issue triage per ISTQB CTAL-TM.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/ahuaracab/test-genesis --skill test-management-ahuaracab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-management
Source: https://github.com/ahuaracab/test-genesis/tree/main/.agents/skills/test-management
Command: npx skills add https://github.com/ahuaracab/test-genesis --skill test-management-ahuaracab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating a multi-person QA team through a sprint or regression program requires constant decisions about who tests what, whether the team is on schedule, and how to respond when blockers or defects appear. This Skill provides a structured five-phase workflow (Plan, Resource Allocate, Monitor, Escalate, Report) aligned to ISTQB CTAL-TM and IEEE 29119-3 so test leads can manage capacity, SLAs, and triage consistently instead of improvising. ## Core Features & Use Cases - Capacity Planning & Skills Matrix: Forecast available hours against test workload, build a skills matrix by specialty and seniority, and detect over-allocation before the sprint starts. - Real-Time Execution Monitoring: Track pass rate, progress vs forecast, blocker queues, and SLA compliance (blocker response <2min, triage <30min, high-severity fix <4h) on a live dashboard. - Severity-Based Issue Triage: Classify findings as Bug, Defect, or Improvement, assign severity via an impact × reproducibility matrix, route to the right assignee, and escalate SLA breaches. - Use Case: A QA lead managing 10 testers and 500 regression cases over 2 days uses the skill to prioritize scope to fit 182 available hours, build a parallel execution DAG, monitor progress, and produce an end-of-sprint report with velocity, defect escape rate, and SLA compliance. ## Quick Start Ask the AI to manage your QA team for the current sprint by providing your team roster, test case count, and available hours so it can run the five-phase test management workflow.

Frequently Asked Questions about test-management

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

FAQPage Schema
How do I plan QA team capacity for a sprint?

Calculate available hours as team size times hours per person times utilization, minus a 20% contingency buffer. Compare that against total test workload (test count times average hours per case type) and flag over-allocation above 110% for descoping or staffing decisions.

How do I triage a defect found during test execution?

Classify it as Bug, Defect, or Improvement based on the feature's lifecycle stage, then assign severity using an impact times reproducibility matrix and priority from business ranking. File the issue in Jira with components and assignee within the 30-minute triage SLA.

What is the difference between severity and priority in defect triage?

Severity measures technical impact combined with reproducibility (Critical through Trivial), while priority is a business ranking from 1 to 5. They are orthogonal: a high-severity defect with high priority triggers immediate escalation.

When should I escalate a test blocker instead of retrying?

Escalate immediately when a test hangs over 2 minutes, an endpoint returns 5xx, fixture setup fails, or environment instability is detected. Retry only for confirmed flaky tests or transient infrastructure issues, up to two attempts with backoff.

When should I not use the test-management skill?

Do not use it for test case design (use test-planning or sprint-testing), automation scaffolding (use test-automation), or TMS artifact publishing (use test-documentation). It focuses on team coordination, monitoring, and triage, not authoring tests.