Skip to main content
rule CX Codex

test-plan — Claude Code rule: what it does, how to install

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.

AGPL-3.0 ★ 267 updated 2026-02-20

Install into Cursor · Manually: put the files in place All methods and platforms ↓
.cursor/rules/test-plan.mdc
Open on GitHub

What test-plan 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.

What it helps with

  • 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 for the agent

  • 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.

How to install test-plan

Manually: put the files in place

.cursor/rules/test-plan.mdc

Frontmatter: description, globs, alwaysApply

Step by step, with commands for each platform: Cursor rules: .mdc files, four modes and what replaced .cursorrules

Questions about test-plan

How do I install test-plan in Claude Code?

Add the rule file at .claude/rules/test-plan.md. Then ask the agent to create a test plan for the project.

What does test-plan do?

It examines the project code and technology stack, then produces a detailed testing plan in Polish Markdown.

What language does test-plan use for its plan?

The resulting plan is written in Polish.

Similar IDE rules

All IDE rules for Testing and QA →

From the same set24

The whole set →
react-development react-development sets coding standards for React components inside an Astro app: hooks over classes, memoization, Tailwind-driven responsiveness. CX Codex +1 ★ 267repo stars github-action Guides Claude Code in generating GitHub Actions workflows with scoped secrets, composite steps, and upstream version checks. CX Codex +1 ★ 267repo stars shadcn-resume-implementation shadcn-resume-implementation is a Claude Code command that resumes frontend work from a saved status. It uses the implementation plan, frontend rules, and type definitions. CX Codex +1 ★ 267repo stars shadcn-plan-summary shadcn-plan-summary — a command that captures decisions from UI architecture sessions. Extracts choices about layout, flows, API integration, and state management, then compiles them into a structured report for the next development phase. CX Codex +1 ★ 267repo stars supabase-migrations This rule guides Claude Code when creating Supabase SQL migrations, from timestamped filenames to RLS policies. It applies to files under supabase/migrations/. CX Codex +1 ★ 267repo stars generate-types-from-supabase generate-types-from-supabase analyzes Supabase schema and generates TypeScript types for DTOs and Command Models. Cuts down manual type definition work by deriving structures from your database. CX Codex +1 ★ 267repo stars vitest-unit-testing vitest-unit-testing is a Claude Code rule for writing Vitest unit tests. It guides module mocking and React component test structure. CX Codex +1 ★ 267repo stars project-prd The project-prd command turns project plans into a structured PRD and saves it as a Markdown file. Use it to draft requirements, user stories, and acceptance criteria. CX Codex +1 ★ 267repo stars

Project sponsors

Companies that keep this analytics open