testspec-generate

Generate test cases from specs and export as Excel or XMind artifacts.

5|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/winhok/testkit --skill testspec-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testspec-generate
Source: https://github.com/winhok/testkit/tree/main/skills/testspec-generate
Command: npx skills add https://github.com/winhok/testkit --skill testspec-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openpyxl, and includes scripts (resource) components.

What problem does it solve?

Automate the end-to-end creation of structured test cases from requirements specs and centralize output as Excel or XMind artifacts, reducing manual drafting time and inconsistencies.

Core Features & Use Cases

  • Reads specs/testpoints.md to derive test points, then expands them into detailed test cases with clear steps and expectations.
  • Exports results as Excel (.xlsx) and XMind (.xMind) formats into the current change's artifacts directory, enabling easy sharing and review.
  • Validates generated JSON via the included validation tools and supports schema v2 testcases with optional tp_refs for traceability.

Quick Start

Use testspec-generate to convert specs into ready-to-run test cases and export artifacts with built-in Python scripts.

Frequently Asked Questions about testspec-generate

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

FAQPage Schema
How do I automatically generate test cases from markdown specs?

To automatically generate test cases from markdown specs, this tool reads your specs/testpoints.md files, expands them into detailed cases with steps and expectations, and validates the output JSON against schema v2 before exporting artifacts.

Can I export generated test cases to Excel and XMind formats?

Yes, you can export generated test cases to Excel and XMind formats, as the built-in Python scripts emit both .xlsx and .xmind artifacts directly into your current change's artifacts directory for easy sharing and review.

Does the test case generation process support traceability back to requirements?

The test case generation process supports traceability through optional tp_refs fields, preserving links from generated test cases back to the original specs and test points for full requirements tracking.

Do I need Python and openpyxl to run the test case export scripts?

You need Python and the openpyxl dependency to run the test case export scripts, as the tool relies on these Python components to read specs, validate JSON structure, and generate the final Excel artifacts.

What is the best way to convert testpoints into structured test cases for review?

The best way to convert testpoints into structured test cases is to automate the drafting process, which reads testpoints.md, expands them into clear steps and expectations, and validates the JSON to ensure consistency before exporting.

Are there limitations when generating test cases from specs within a change directory?

The main limitation is that the tool operates strictly within the current change directory, reading specs/testpoints.md and writing artifacts locally, so you must ensure your spec files are correctly placed before running the generation scripts.