Agent skill
writing-test-plans
Creates risk-based test plans and strategies. Use when planning testing, defining test scope, or documenting QA approach.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/writing-test-plans
SKILL.md
Test Plan Writing
Create practical, risk-based test plans.
Right-Size the Plan
Small feature: One-page plan (scope, risks, approach). Large feature: Full plan with all sections. Ask "Does the reader need this?" for every section.
Risk-Based Prioritization
| Risk/Impact | High Impact | Low Impact |
|---|---|---|
| High Risk | Test thoroughly | Test defensively |
| Low Risk | Test key paths | Minimal testing |
Test Pyramid
/ E2E \ Few, slow, expensive
/ Integ. \ Some, moderate
/ Unit \ Many, fast, cheap
Required Sections
-
Overview - Feature under test, objectives, link to spec
-
Scope - In scope (what tested), Out of scope (what not, and why)
-
Test Strategy - Test types, approach per component, automation decisions
-
Risk Assessment - Identified risks, severity, mitigation, attention areas
-
Test Cases - Organized by feature, priority (P0/P1/P2), happy path and edge cases
-
Environment & Data - Test environments, data requirements, dependencies
-
Entry/Exit Criteria - When testing starts, when testing is complete
Test Case Format
### TC-001: [Description]
**Priority**: P0 | P1 | P2
**Type**: Unit | Integration | E2E | Manual
**Preconditions**:
- [Required state]
**Steps**:
1. [Action]
**Expected Result**:
- [Outcome]
**Edge Cases**:
- [Variations]
Priority Definitions
| Priority | Description | Coverage |
|---|---|---|
| P0 | Critical path, must work | 100% automated |
| P1 | Important functionality | Mostly automated |
| P2 | Edge cases | Manual or deferred |
Test Types
| Type | Purpose | When |
|---|---|---|
| Unit | Isolated functions | Business logic, utilities |
| Integration | Component interactions | APIs, database, services |
| E2E | Complete user flows | Critical journeys |
| Manual | Exploratory, UX | Complex UI, accessibility |
Guidelines
Link tests to requirements. Prefer automation. Test behavior, not implementation. Keep tests simple.
Anti-Patterns
Do not test implementation details. Do not target 100% coverage as a goal. Do not create flaky tests. Do not rely on specific timing or order. Do not mock everything.
Template
Use templates/test-plan.md for new plans.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?