plan-test-create

Generates complete task plans from approved design blueprints and user requirements documents.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill plan-test-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-test-create
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/plan-test-create
Command: npx skills add https://github.com/oogDZ/2 --skill plan-test-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a comprehensive test plan automatically from Design (SVC-N, INT-N, STS-N) and Discussion (REQ-N) materials, ensuring traceability and readiness for validation.

Core Features & Use Cases

  • Automates the extraction of acceptance criteria, test data, system scenarios, and coverage matrices from design artifacts.
  • Supports end-to-end test plan generation aligned with a Design-driven workflow and WAITING state handling.
  • Example: given a design in WAITING, generates a complete test plan ready for test development.

Quick Start

Run /plan-test-create <parent-design> to generate the test plan from Design and Discussion when the Design is WAITING.

Frequently Asked Questions about plan-test-create

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

FAQPage Schema
How do I generate a test plan from design artifacts?

To generate a test plan from design artifacts, run the /plan-test-create command on a parent design. It automatically extracts acceptance criteria, test data, system scenarios, and coverage matrices from your design and discussion materials.

What is design-driven test strategy and traceability?

Design-driven test strategy derives validation scenarios directly from design artifacts like SVC-N and INT-N. Traceability ensures every test case maps back to a specific design element and discussion requirement, guaranteeing full validation coverage.

How do I create acceptance criteria and test data from system scenarios?

You can create acceptance criteria and test data from system scenarios by applying the /plan-test-create workflow. It parses STS-N and REQ-N materials to automatically generate matching test inputs and expected validation outcomes.

Does design state need to be WAITING before generating a test plan?

Yes, the design state must be WAITING before generating a test plan. The /plan-test-create workflow expects this deterministic state to ensure the design and discussion materials are fully finalized for extraction.

Can I build a coverage matrix from discussion requirements?

Yes, you can build a coverage matrix from discussion requirements. The tool automatically parses REQ-N materials and maps them against extracted system scenarios to produce a complete validation coverage matrix.

What are the limitations of automating end-to-end test plan generation?

A limitation of automating end-to-end test plan generation is its strict dependency on existing design and discussion artifacts. Without properly structured SVC-N, INT-N, STS-N, and REQ-N inputs in a WAITING state, it cannot produce the test plan.