generator_skill

This skill automatically generates mixed-structure Markdown test cases from requirements, supporting markmap rendering and multiple testing types to accelerate
  • Shell

0

GitHub Stars

2

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill mookechee/casepilot --skill generator

  • SKILL.md9.3 KB
  • TEMPLATE.md7.9 KB

Overview

This skill is an intelligent test case generator that converts requirements, stories, defects, or technical design documents into structured Markdown test cases suitable for markmap visualization. It supports multiple test types—functional, boundary, exception, compatibility, performance, and security—and outputs a standardized markmap-ready Markdown file. The skill can read Feishu/Lark project items, cloud docs, or local files and produces a seven-level mixed-structure test case tree with priority tagging.

How this skill works

The generator follows a four-stage progressive pipeline: requirement analysis, test point extraction, test case design, and intelligent optimization. It can fetch Feishu project items and cloud docs via configured MCP connectors or ingest local files. It analyzes PRD UI and interaction flows, optionally augments coverage with web search references, then produces markmap-compatible Markdown using a fixed 7-layer structure and standardized priority labels (P0/P1/P2).

When to use it

  • You need markmap-renderable Markdown test cases from a story, requirement, or defect.
  • You have Feishu/Lark project URLs or cloud doc links and want automated test coverage.
  • You want a mix of functional, boundary, abnormal, compatibility, performance, or security tests.
  • You want a reproducible Markdown output following a strict 7-layer structure and priority rules.
  • You prefer automated extraction of UI components, user flows, and acceptance criteria into test cases.

Best practices

  • Provide a clear Feishu project URL, cloud doc link, or a well-formed local requirement file for best results.
  • Ensure MCP connectors (lark-prj-remote and lark-mcp-remote) are configured when using Feishu resources.
  • Include acceptance criteria and technical design links in the source to guarantee coverage of must-have checks.
  • Review the generated user flow and decision points before finalizing test cases to catch domain-specific nuances.
  • Use the generated file path convention (~/Testcase/markmap/{item}_测试用例_{timestamp}.md) to keep outputs organized.

Example use cases

  • Generate markmap test cases from a Feishu story URL to hand to QA for execution planning.
  • Create a comprehensive test coverage matrix from a technical design doc for performance and security checks.
  • Produce boundary and negative tests for an API based on PRD UI and interaction analysis.
  • Auto-generate a mind-map style test suite for multi-platform compatibility testing.
  • Convert local requirement markdown files into standardized test case documents for CI integration.

FAQ

If MCP connectors are missing, the skill will prompt configuration steps and you can still use local files without MCP.

How are priorities assigned?

Priorities follow P0/P1/P2 rules: P0 for core flows and acceptance criteria, P1 for important and boundary checks, P2 for optional stability or auxiliary tests.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational