test-planner

Generates structured test plans from requirement, design, or API design documents.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/HACK-WU/skills --skill test-planner-hack-wu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-planner
Source: https://github.com/HACK-WU/skills/tree/main/skills/test-planner
Command: npx skills add https://github.com/HACK-WU/skills --skill test-planner-hack-wu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing test plans by hand often produces vague checklists with no traceability to requirements, no coverage visibility, and no clear path to executable test code. This Skill reads your source documents and produces a complete, traceable test plan with concrete steps, expected results, and pass criteria. ## Core Features & Use Cases - Three Source Modes: Generates tests from requirement documents (acceptance criteria mapped to 7 test strategies), design documents (design points, interfaces, data flows), or API design documents (contracts, error codes, auth, idempotency). - Strategy-Based Case Generation: Matches acceptance criteria keywords to functional, negative, metric, performance, security, data, and experience test strategies, including positive and negative UX (error guidance, foolproofing, adversarial input) cases. - Coverage Matrix & Traceability: Every test case traces back to a specific REQ entry, design point, or API endpoint, with a coverage matrix showing which items are tested and which are not. - Test Code Placement Guidance: Scans the project for existing test directory conventions, frameworks, and run commands, then annotates each module with executability status so the plan can land as runnable test code. - Use Case: After running requirement-mining for a user registration feature, invoke this Skill to produce a test-plan.md with 20+ cases covering normal paths, boundary conditions, permission denial, performance thresholds, and risk-based scenarios. ## Quick Start Ask the AI to generate a test plan from the requirement.md, DESIGN.md, or api-design.md in your project, and it will produce a traceable test-plan.md with a coverage matrix and test code placement guidance.

Frequently Asked Questions about test-planner

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

FAQPage Schema
How do I generate a test plan from a requirements document?

Provide the path to your requirement.md and the Skill parses each REQ entry's acceptance criteria, matches keywords to one of seven test strategies, and generates test cases with preconditions, steps, expected results, and pass criteria. Output is written to test-plan.md with a coverage matrix.

How to create API contract tests from an API design document?

In API design mode, the Skill extracts endpoints, request/response schemas, error codes, and auth requirements from api-design.md. Each endpoint gets contract conformance, parameter boundary, error code trigger, and authorization cases, plus idempotency and concurrency cases for write operations.

What test strategies does it use for acceptance criteria?

Seven strategies are matched by keywords: functional, negative, metric, performance, security, data, and experience. Security takes priority when multiple strategies match, and functional requirements always include normal path, exception path, and boundary condition cases.

Does it decide where test code files should be placed?

Yes. It scans the project for existing test directories, config files like pytest.ini or package.json, and framework conventions rather than assuming fixed paths. Each module is annotated with test location, framework, run command, and an executability status such as runnable, environment-dependent, or unknown.

When should I not use this test plan generator?

Skip it when you want test code written directly in pytest or jest, when no source document (requirement, design, or API design) exists, or when you only have a quick question about how to write tests. It is designed for full plan generation, not ad-hoc coding.

How does it verify test coverage of requirements?

It runs quality checks confirming every REQ has at least one case or an explicit uncovered reason, P0 requirements are fully covered, and the coverage matrix IDs match actual cases. It also checks that numeric criteria have metric or performance cases and negative criteria have denial cases.