# test-plan

test-plan is a Claude Code rule that builds a project-specific test plan from the codebase and tech stack. It writes the result in Polish as Markdown.

- rule · `type=rule` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline · ★ 267 repo stars
- Author: przeprogramowani
- License: AGPL-3.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/przeprogramowani/ai-rules-builder/tree/HEAD/.cursor/rules/test-plan.mdc
- Updated: 2026-02-20
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/rules/test-plan

## What it does

test-plan examines the project and drafts a detailed testing plan based on its code, repository structure, and technologies. It also reads `.ai/tech-stack.md` for information about the stack.

The plan covers testing goals and scope, test categories, scenarios, tools, and the test environment. It also sets out a schedule, acceptance criteria, team responsibilities, and a process for reporting bugs. The output is the plan alone, in Polish Markdown.

The project code and `.ai/tech-stack.md` are needed for the analysis; the file supplies the technology-stack details.

## Install

### Cursor (native platform)

**Manually: put the files in place**
- File: `.cursor/rules/test-plan.mdc` — Frontmatter: description, globs, alwaysApply

### Claude Code

**Manually: put the files in place**
- File: `.claude/rules/test-plan.md` — The paths frontmatter field limits the files: move globs from the source into paths

### Codex

**AGENTS.md**
- Codex reads AGENTS.md: paste the rule text there

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/instructions/test-plan.instructions.md` — The applyTo field sets which files it applies to: move globs from the source into applyTo

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/rules/test-plan.md`

### Cline

**Manually: put the files in place**
- File: `.clinerules/test-plan.md`

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/przeprogramowani/ai-rules-builder/tree/HEAD/.cursor/rules/test-plan.mdc

## When to use it
- build a test plan around a repository’s structure
- prioritize the project areas that need testing
- define test scenarios, acceptance criteria, and bug-reporting steps

## Example prompts
- Create a Polish test plan for this project using its code and `.ai/tech-stack.md`.
- Draft a Markdown test plan covering the repository’s key components.
- Add test categories, acceptance criteria, and a bug-reporting process to the project plan.

## Similar
- [create-test-cases](https://affpapa.org/en/nevibecode/commands/create-test-cases.md) — command · ★ 406 repo stars
- [test-scenarios](https://affpapa.org/en/nevibecode/commands/test-scenarios.md) — command · ★ 28211 repo stars
- [accessibility-test-plan](https://affpapa.org/en/nevibecode/skills/accessibility-test-plan.md) — skill · 2400 installs
- [qa-plan](https://affpapa.org/en/nevibecode/skills/qa-plan.md) — skill · 671 installs
- [breakdown-test](https://affpapa.org/en/nevibecode/skills/breakdown-test.md) — skill · 9264 installs
- [jmeter-test-plan-creator](https://affpapa.org/en/nevibecode/skills/jmeter-test-plan-creator.md) — skill · 107 installs

From the same set: [przeprogramowani/ai-rules-builder](https://affpapa.org/en/nevibecode/by/przeprogramowani/ai-rules-builder.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
