test-plan-generator

Generates test plan documents with test cases and defect tracking tables from requirements.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/jacksonlee-tw/mystock-vue --skill test-plan-generator-jacksonlee-tw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-plan-generator
Source: https://github.com/jacksonlee-tw/mystock-vue/tree/main/mystock-analysis/.github/skills/test-plan-generator
Command: npx skills add https://github.com/jacksonlee-tw/mystock-vue --skill test-plan-generator-jacksonlee-tw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing test plans and test cases from scratch is repetitive and error-prone, especially when teams must follow a consistent document template. This Skill turns module requirements, Use Cases, API specs, or plain descriptions into a complete, template-compliant test plan document. ## Core Features & Use Cases - Template-Driven Generation: Reads the project's standard test plan template and produces documents with matching sections: objectives, scope, schedule, acceptance criteria, test cases, and defect tracking. - Multi-Source Input: Accepts Use Case documents, API specifications, DB specs, existing code, bug reports, or verbal descriptions, and derives positive and negative test cases automatically. - Structured Test Cases: Generates numbered test cases (TC-001...) with concrete steps, expected results, and priority levels, plus a defect tracking table (BUG-001...). - Use Case: Given a login module's Use Case and API spec, produce a ready-to-deliver QA document covering UI tests, API tests, integration tests, and regression cases. ## Quick Start Ask the assistant to generate a test plan for your module based on its Use Case or API specification document.

Frequently Asked Questions about test-plan-generator

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

FAQPage Schema
How do I generate a test plan from a Use Case document?▼

Provide the Use Case file path or describe the module, and the Skill reads the project test plan template, then derives one test case per main and alternative flow. Output includes objectives, scope, schedule, and numbered test cases.

How to create test cases from an API specification?▼

Supply the API spec document and the Skill generates at least one positive and one negative test case per endpoint, covering response format, status codes, and field correctness. Cases follow the TC-001 numbering format with priority levels.

What inputs does a test plan generator accept?▼

It accepts Use Case documents, API specifications, DB specs, existing source code such as controllers or Vue pages, bug reports for regression tests, feature lists, or plain verbal descriptions of the functionality to test.

Can I update an existing test plan when features change?▼

Yes. When features are modified, added, or removed, the Skill can synchronize the corresponding test plan by adding new test cases, supplementing test items, or updating existing entries while keeping numbering consistent.

What are the limitations of template-based test plan generation?▼

The output strictly follows the project's Markdown template structure, so it requires the template file to exist at the configured path. Missing details like dates or owners are left as placeholders such as YYYY-MM-DD or TBD for manual completion.