speckit-test-plan

Map requirements and risks to negotiated test-case plans.

95|39|Updated Dec 15, 2025

Search Tags:#validation #regression #e2e testing #api testing #spec-kit #test planning

Ready to run

npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-test-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit-test-plan
Source: https://github.com/liuminxin45/auto-podcast/tree/main/.agents/spec-kit/skills/speckit-test-plan
Command: npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-test-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns changing requirements into a compact, negotiated test-case plan so teams can agree on validation scope before implementation begins.

Core Features & Use Cases

Scenario-to-test mapping: Connects each requirement or risk to API, E2E, regression, fixture, smoke, or manual coverage.
Review gating: Determines whether the plan is ready to proceed or needs human review when behavior, contracts, or accepted gaps are still ambiguous.
Artifact updates: Writes the agreed plan back into spec and plan documents so later work can continue with clear validation intent.
Use Case: A product team changes a public contract and needs a minimal test plan that covers impacted API behavior, visible workflow changes, and any deliberate coverage gaps.

Quick Start

Ask the AI to draft a negotiated test-case plan for the active spec and update the plan artifacts with the resulting review status.

Frequently Asked Questions about speckit-test-plan

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

FAQPage Schema

How do I negotiate a test plan before implementation begins?▼

Review gating determines whether a test plan proceeds or needs human review by evaluating behavior, contracts, and accepted coverage gaps. When ambiguity exists in API changes or workflows, the gating mechanism pauses automation to force manual validation of the negotiated test scope.

How do I map requirement scenarios to API and E2E test cases?▼

Scenario-to-test mapping connects each requirement or risk to specific validation types including API, E2E, regression, fixture, smoke, or manual coverage. This mapping ensures every public contract change or visible workflow shift has a corresponding test-case plan documented in spec.md and plan.md.

Does spec-kit workflow support automated regression and fixture coverage planning?▼

Spec-kit workflows support automated regression and fixture coverage planning through negotiated test-case plans. The workflow maps requirements to specific coverage types, updates spec and plan documents with review status, and gates progression when behavior or contracts remain ambiguous.

What is the best way to update spec.md and plan.md with a negotiated test-case plan?▼

The best way to update spec.md and plan.md is by writing the agreed validation scope and review status directly into the artifacts. This maps requirements to API, E2E, and regression coverage, ensuring downstream implementation continues with clear, documented test intent.

When should I use manual coverage instead of automated E2E testing in a test plan?▼

Manual coverage should be used when behavior, public contracts, or accepted gaps remain ambiguous during test plan negotiation. The review gating mechanism identifies these scenarios, pausing automated E2E or API validation to require human review before proceeding with implementation.