planning-testing-strategy

Transform acceptance criteria, API specs, and security controls into a unified testing strategy.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gleeb/ai-registry --skill planning-testing-strategy-gleeb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-testing-strategy
Source: https://github.com/gleeb/ai-registry/tree/main/systems/sdlc/skills/planning-testing-strategy
Command: npx skills add https://github.com/gleeb/ai-registry --skill planning-testing-strategy-gleeb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents late surprises by turning scattered acceptance criteria, API specs, and security controls into a single, enforceable cross-cutting testing strategy with clear coverage mapping and CI/CD test gates.

Core Features & Use Cases

  • Acceptance criteria inventory & coverage mapping: Extracts and categorizes acceptance criteria (unit, integration, E2E, manual) and traces them back to story artifacts.
  • Test pyramid & specialized plans: Designs the test pyramid and expands it into API, security, accessibility (WCAG 2.2 AA), and performance testing guidance.
  • CI/CD test gates & coverage thresholds: Defines which tests run per pipeline stage and specifies coverage thresholds, negative testing requirements, and enforcement expectations.
  • Strategy output: Writes the final cross-cutting plan to plan/cross-cutting/testing-strategy.md.

Quick Start

Ask the Planning Hub testing dispatcher to use planning-testing-strategy after Phase 3 so it can read per-story artifacts and produce plan/cross-cutting/testing-strategy.md.

Frequently Asked Questions about planning-testing-strategy

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

FAQPage Schema
How do I create a cross-cutting testing strategy from acceptance criteria and API specs?

A cross-cutting testing strategy transforms scattered acceptance criteria, API specs, and security controls into a single enforceable plan with coverage mapping and CI/CD test gates, preventing late-stage integration surprises.

How do I design a test pyramid with integration and E2E scenarios for CI/CD?

Design a test pyramid by structuring unit, integration, and E2E layers, expanding into API, security, accessibility, and performance coverage, then defining which tests execute per pipeline stage with specific coverage thresholds.

What is the best way to map acceptance criteria to automated test coverage thresholds?

Map acceptance criteria to coverage by extracting and categorizing criteria into unit, integration, E2E, and manual buckets, tracing them back to story artifacts, and enforcing coverage thresholds within CI/CD test gates.

Does my testing strategy need to include accessibility and performance testing plans?

Yes, a comprehensive testing strategy should include specialized plans for accessibility testing aligned with WCAG 2.2 AA standards, alongside performance testing guidance, to ensure complete cross-cutting coverage.

How do I configure CI/CD test gates to enforce negative testing requirements?

Configure CI/CD test gates by defining specific test executions per pipeline stage, setting mandatory coverage thresholds, and enforcing negative testing requirements to block deployments that fail these cross-cutting checks.