skills.rest
EnigmaWU
EnigmaWUCOMMUNITY
Explore all skills by this author →
GitHub

apply-agile-testing-quadrants

Categorize and plan tests across four Agile Testing Quadrants.

1|Updated Apr 6, 2026
Search Tags:#quality assurance#test strategy#test planning#quadrants#agile testing
One-click install
npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill apply-agile-testing-quadrants
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: apply-agile-testing-quadrants
Source: https://github.com/EnigmaWU/MyCodeAgentSkills/tree/main/apply-agile-testing-quadrants
Command: npx skills add https://github.com/EnigmaWU/MyCodeAgentSkills --skill apply-agile-testing-quadrants

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps ensure a comprehensive test strategy by applying Agile Testing Quadrants, balancing test coverage across different dimensions.

Core Features & Use Cases

  • Apply Agile Testing Quadrants: Categorize and plan tests across four quadrants: Q1 (Technology/Support), Q2 (Business/Support), Q3 (Business/Critique), and Q4 (Technology/Critique).
  • Test Strategy Definition: Supports defining a testing strategy for features, sprint planning, and acceptance criteria.
  • Resource Mapping: Identifies testing gaps and provides a categorized list of proposed tests mapped to the quadrants.

Quick Start

Apply the Agile Testing Quadrants to your new feature's test strategy using the apply-agile-testing-quadrants skill.

Frequently Asked Questions about apply-agile-testing-quadrants

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

FAQPage Schema
What is the best way to balance test coverage across business and technology dimensions?▼

Agile Testing Quadrants balance test coverage by categorizing tests into four distinct quadrants spanning business and technology dimensions, ensuring a comprehensive test strategy. This approach identifies testing gaps and maps proposed tests systematically.

How do I categorize tests using Agile Testing Quadrants?▼

You categorize tests into four quadrants: Q1 covers Technology/Support, Q2 addresses Business/Support, Q3 handles Business/Critique, and Q4 targets Technology/Critique. This classification maps tests to specific testing dimensions.

Do I need any specific testing frameworks to apply this test strategy?▼

No specific testing frameworks are required to apply this test strategy. The approach is framework-agnostic, focusing on categorizing and planning tests logically across support and critique dimensions rather than relying on external dependencies.

When should I use Agile Testing Quadrants for test planning?▼

Use Agile Testing Quadrants during feature design, sprint planning, and acceptance criteria writing. It is intended for these early stages to define a testing strategy that identifies gaps and provides a categorized list of proposed tests.

What are the limitations of using quadrants for agile test planning?▼

Quadrants focus on categorizing and planning tests rather than executing them or automating test scripts. It provides a strategic map for test coverage but does not directly generate or run technical test cases for the application.

Related Skills

Explore More Software Engineering Skills→
jshsakurajshsakura
22

qa-expert

Define risk-based test scope and acceptance criteria for software releases.

Community
Advanced
Eigo-Mt-FujiEigo-Mt-Fuji

quality-assurance

Creates comprehensive QA strategies and test plans for software projects.

Community
Advanced
Lifecycle-Innovations-LimitedLifecycle-Innovations-Limited
22

ops-linear

Manage Linear issues and sprint planning via MCP tools.

Official
Advanced
summarybotngsummarybotng
2

risk-based-testing

Assess and prioritize software testing risks by probability and impact.

Official
Advanced