skills.rest
mattgierhart
mattgierhartCOMMUNITY
Explore all skills by this author →
GitHub

prd-v07-test-planning

Plan TEST- entries with Given-When-Then templates linked to EPIC-, API-, BR-, and UJ- identifiers.

193|9|Updated Jul 10, 2025
Search Tags:#acceptance-criteria#given-when-then#test-planning#epic-linking#qa-process#test-entries
One-click install
npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v07-test-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-v07-test-planning
Source: https://github.com/mattgierhart/PRD-driven-context-engineering/tree/main/.claude/skills/prd-v07-test-planning
Command: npx skills add https://github.com/mattgierhart/PRD-driven-context-engineering --skill prd-v07-test-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In many projects, tests are an afterthought. This Skill helps teams predefine TEST- entries and acceptance criteria before implementation, ensuring clear expectations and testable outcomes.

Core Features & Use Cases

  • Define TEST- entries linked to EPICs to capture test intent early.
  • Support Type coverage (Unit, Integration, E2E, Contract, Performance) and mappings to BR- and UJ- to enable comprehensive QA planning.
  • Provide a reusable TEST- template and guidance that ensures traceability from EPICs through implementation.

Quick Start

Create TEST-001 for the initial API endpoint and link it to EPIC-01.

Frequently Asked Questions about prd-v07-test-planning

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

FAQPage Schema
How do I write acceptance criteria for test planning before implementation?▼

You can plan test coverage upfront by creating TEST- entries linked to EPICs, supporting Unit, Integration, E2E, Contract, and Performance types mapped to BR- and UJ- identifiers for comprehensive QA planning.

What is the Given-When-Then template used for in test planning?▼

The Given-When-Then template provides a standardized structure for defining test entries, ensuring traceability from EPICs through implementation and enabling clear measurement across API endpoints, BR rules, and UJ journeys.

Can I link test entries to multiple identifiers like API endpoints and business rules?▼

Yes, TEST- entries can be linked to multiple identifiers including EPIC-, API-, BR-, and UJ- identifiers, providing comprehensive traceability and test coverage across PRD v0.7 components.

How do I create a test entry for an API endpoint using the test planning template?▼

To create a test entry, start by defining TEST-001 for the initial API endpoint and link it to EPIC-01, using the standardized template to capture test intent early and ensure testable outcomes.

What types of test coverage are supported for QA planning?▼

Supported test coverage types include Unit, Integration, E2E, Contract, and Performance testing, with mappings to BR- and UJ- identifiers to enable comprehensive QA planning and verifiable acceptance criteria.

When should I define test entries in the product development lifecycle?▼

Test entries should be planned upfront before implementation begins, ensuring clear expectations and testable outcomes are locked in rather than treating tests as an afterthought during development.

Related Skills

Explore More Product & Management Skills→
mattgierhartmattgierhart
193

prd-v04-screen-flow-definition

Translate user journeys into screen-flow inventories with SCR- and DES- entries.

Community
Advanced
apassuelloapassuello

automating-api-testing

Generate and execute API tests for REST and GraphQL endpoints.

Community
Intermediate
jmaglyjmagly
175

traceability-check

Maps requirements to code and tests, computes coverage gaps and generates a traceability report.

Community
Intermediate
jpoleyjpoley
50

qa-validator

Plan, execute, and validate software quality through structured QA workflows.

Community
Basic