Agent skill
test-plan-generator
Automatically generate comprehensive QA test plans when user mentions testing requirements, QA needs, or asks what should be tested. Analyzes code changes and features to create structured test scenarios. Invoke when user mentions "test plan", "QA", "what to test", "testing requirements", or "test scenarios".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/test-plan-generator-kanopi-cms-cultivator
SKILL.md
Test Plan Generator
Automatically generate comprehensive QA test plans based on features and changes.
When to Use This Skill
Activate this skill when the user:
- Asks "what should QA test?"
- Says "I need a test plan"
- Mentions "testing requirements" or "test scenarios"
- Shows a new feature and asks "how should this be tested?"
- Asks "what test cases do I need?"
- References QA, testing coverage, or manual testing
Quick Reference
See /test-plan command documentation for detailed test plan structure and examples.
This skill provides the same comprehensive test plan generation but is automatically invoked during conversation when the user expresses a need for test planning.
Integration with /test-plan Command
-
This Skill: Auto-invoked conversationally
- "What should I test for this feature?"
- "Need test scenarios"
-
/test-planCommand: Explicit comprehensive generation- Full project test plan generation
- Git history analysis
- Structured documentation output
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
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.
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.
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.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
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?