prd-v07-test-planning_skill

Overview

This skill defines test cases before implementation to ensure every API, business rule, database table, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. It converts EPIC-, API-, DBT-, BR-, and UJ- inputs into formal TEST- entries in Given–When–Then format. Use it to enforce a test-first contract that feeds the v0.7 Implementation Loop and CI/CD pipelines.

How this skill works

On trigger phrases like "define tests" or "test planning", the skill ingests EPIC- scope and linked IDs (API-, DBT-, BR-, UJ-) and generates TEST- entries. For each artifact it produces appropriate test types (Unit, Integration, E2E, Contract, Performance) with happy and error paths, boundary cases, and validation method and automation hints. Outputs follow a consistent TEST- template ready to be linked back to the EPIC and used for automation and review.

When to use it

• At PRD v0.7 Build Execution when scoping an EPIC
• When asking "what to test?" or requesting "test coverage" for APIs, rules, DB schema, or journeys
• Before any implementation work or PR to define acceptance criteria
• When preparing CI/CD test suites and automation plans
• To convert BR-, API-, DBT-, UJ- artifacts into traceable TEST- entries

Best practices

• Write TEST- entries before coding so tests become the contract for "done"
• Ensure every API- has at least one happy path and one error case test
• Create one BR- test per rule including positive, negative, and boundary cases
• Define one E2E TEST- per core UJ- to validate full user value flow
• Mark critical tests for automation and provide file path guidance for implementers

Example use cases

• Generate TEST- entries for a new user signup EPIC with API-, BR-, DBT-, and UJ- links
• Plan test coverage for an API surface: happy path, auth failure, validation error
• Define DB constraint tests for a new table and RLS policy enforcement
• Produce E2E onboarding tests that verify KPI events and session state
• Create unit tests for rule validation functions (password rules, uniqueness)