Test Plan Generator

Community

Firstp1ck

test-plan-generator

Agents should invoke this skill when planning tests from specs, architecture docs, PRs, risky changes, new features, bug fixes, or release work. Generates prioritized unit, integration, E2E, regression, and edge-case coverage.

Overview

Publisher	Firstp1ck
Repository	`pi-coding-agent-forge`
Skill name	`test-plan-generator`
Stars	93
Forks	22
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Firstp1ck on GitHub. Read the source before you install it.

Installation

Install the Test Plan Generator AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-skill-test-plan-generator/skills/test-plan-generator
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-skill-test-plan-generator/skills/test-plan-generator

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forge.git /tmp/pi-coding-agent-forge
mkdir -p .claude/skills
cp -r /tmp/pi-coding-agent-forge/pi-skill-test-plan-generator/skills/test-plan-generator .claude/skills/test-plan-generator

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Test Plan Generator in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Test Plan Generator on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Test Plan Generator is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Test Plan Generator

Generate structured, prioritized test plans from spec and architecture documents.

Inputs

projects/<project-name>/combined-plan.md (primary source of truth)
projects/<project-name>/spec.md (original requirements)
projects/<project-name>/architecture.md (module boundaries and interfaces)
Forge's completion report (existing test coverage)

Process

Step 1 — Extract Requirements

Read the combined plan and extract every testable requirement:

Explicit acceptance criteria from the spec
Interface contracts from the architecture
Security constraints from Zero's review
Error handling expectations
Edge cases mentioned in the spec
Non-functional requirements (performance, accessibility)

Step 2 — Derive Test Cases

For each requirement, create one or more test cases:

markdown
| ID | Requirement | Test Case | Category | Priority | Status |
|---|---|---|---|---|---|
| TC-001 | User can create account | Valid email + password creates account | E2E | P0 | Pending |
| TC-002 | User can create account | Duplicate email rejected with error | E2E | P0 | Pending |
| TC-003 | Email validation | Invalid format "foo@" rejected | Unit | P1 | Pending |
| TC-004 | Rate limit on login | 6th attempt within 1 min returns 429 | Integration | P1 | Pending |

Step 3 — Prioritize

Use this priority scheme:

Priority	Criteria	Examples
P0 (Must test)	Core user flows, data integrity, auth	Login, create, read, update, delete
P1 (Should test)	Error handling, edge cases, security functional	Invalid input, rate limits, empty states
P2 (Nice to test)	Boundary values, concurrent access, rare paths	Max-length input, simultaneous edits
P3 (If time allows)	Cosmetic, UX polish, accessibility	Layout consistency, keyboard navigation

Step 4 — Coverage Analysis

Compare test cases against spec requirements:

markdown
## Coverage Matrix

| Spec Section | Requirements | Test Cases | Coverage |
|---|---|---|---|
| Authentication | 5 | 12 | 100% |
| User Profile | 3 | 6 | 100% |
| Data Export | 2 | 1 | 50% — missing error path tests |

Output Format

markdown
# Test Plan — <Project Name>

**Generated:** YYYY-MM-DD
**Spec Version:** [commit hash or date]
**Total Test Cases:** N
**Coverage:** X% of spec requirements mapped

## Test Cases by Priority

### P0 — Must Test
[Table of P0 test cases]

### P1 — Should Test
[Table of P1 test cases]

### P2 — Nice to Test
[Table of P2 test cases]

### P3 — If Time Allows
[Table of P3 test cases]

## Coverage Gaps

[List of spec requirements without test cases]

## Test Execution Order

1. [Recommended execution sequence based on dependencies]

Watchdog skill — Test plan generation and coverage analysis

Frequently asked questions

What does the Test Plan Generator AI skill do?

Why use Test Plan Generator on TypingMind?

Because you install it once and use it with any model. Test Plan Generator is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Test Plan Generator in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-skill-test-plan-generator/skills/test-plan-generator. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Test Plan Generator?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Test Plan Generator?

As many as you like. As long as a model supports skills, you can use Test Plan Generator with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Test Plan Generator AI skill free?

Yes. It is published on GitHub by Firstp1ck under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Slack E2e

openclaw

OrganizationPopular

Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

Telegram E2e Userbot

Prove user-visible OpenClaw Telegram behavior on Telegram's Test Server with Convex-leased team credentials; drive real-user turns and record messages, edits, deletions, reactions, typing, or rich…

Module Regression

Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed…

Test Collaboration

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Test Plan Generator

Inputs

Process

Step 1 — Extract Requirements

Step 2 — Derive Test Cases

Step 3 — Prioritize

Step 4 — Coverage Analysis

Output Format

Frequently asked questions

Related AI Skills

Set up your own AI workspace now