test-plan

Generate structured test plans for code without writing test code.

71|7|Updated Apr 4, 2026

Search Tags:#automation #testing #analysis #plan #code #test

Ready to run

npx skills add https://github.com/mbwsims/claude-universe --skill test-plan-mbwsims

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-plan
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/test-plan
Command: npx skills add https://github.com/mbwsims/claude-universe --skill test-plan-mbwsims

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps developers create a comprehensive test plan by analyzing code, extracting contracts, and mapping input categories before any test code is written.

Core Features & Use Cases

Analyzes target code to extract signatures, return values, exceptions, and side effects.
Decomposes the input space into canonical, empty, boundary, invalid, and adversarial categories with prioritized test cases.
Recommends appropriate test architecture (unit, integration, or both) and identifies which external systems to mock.
Generates a structured test plan table for each function or module, ready for developers or the /test skill.

Quick Start

Ask the test‑plan skill to create a test plan for the function processOrder in order.js.

Frequently Asked Questions about test-plan

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

FAQPage Schema

How do I create a structured test plan for a function without writing test code?▼

To create a structured test plan without writing test code, you analyze the target code to extract signatures and return values, decompose the input space into canonical, boundary, and invalid categories, and map out test architecture and mock boundaries.

When do I need to decompose the input space before writing tests?▼

You need to decompose the input space before writing tests when planning comprehensive coverage for complex modules, ensuring you capture canonical, empty, boundary, invalid, and adversarial input categories to prioritize test cases effectively.

How do I identify which external systems to mock for a module test architecture?▼

To identify which external systems to mock for a module test architecture, you extract code contracts and side effects using file reading and pattern matching tools, then recommend mock boundaries based on the extracted dependencies.

Can I generate a test plan for a specific module like order.js without coding?▼

Yes, you can generate a test plan for a specific module like order.js without coding by instructing the tool to analyze the target function, extract its contracts, and output a structured test plan table ready for developers.

What is the best way to define input categories for unit and integration testing?▼

The best way to define input categories for unit and integration testing is to analyze target code contracts and decompose the input space into canonical, empty, boundary, invalid, and adversarial categories with prioritized test cases.

What are the limitations of generating a test plan without writing any test code?▼

Generating a test plan without writing test code is limited to analysis, contract extraction, and planning; it outputs a structured table and architecture recommendations but does not execute tests or generate the actual test code itself.