| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.9 KB |
| references/CHANGE-SUMMARY.md | markdown | 9.8 KB |
| references/TEST-CASES.md | markdown | 4.1 KB |
| references/TEST-PLAN.md | markdown | 3.8 KB |
| templates/CHANGE-SUMMARY.md | markdown | 1.1 KB |
| templates/TEST-CASES.md | markdown | 680 B |
| templates/TEST-PLAN.md | markdown | 2.1 KB |
templates/TEST-PLAN.md
View on GitHub## Test Plan: [Task / MR / Feature Name]
**Date:** [YYYY-MM-DD]
**Branch / Version:** [branch-name / v1.2.3]
**Environment:** [staging / development / local]
---
### 1. Testing Goal
[What we are verifying and why. Brief: what functionality changed and whether it works correctly.]
---
### 2. Test Scope
**In Scope** β we test:
- [Component / feature 1]
- [Component / feature 2]
**Out of Scope** β we don't test:
- [What is excluded and why]
---
### 3. Test Types
| Type | Priority | Area |
|-------------------|------------|----------------------------------------|
| Functional | π΄ High | [Core changed functions] |
| Regression | π‘ Medium | [Adjacent functionality] |
| Edge cases | π‘ Medium | [Input edge cases] |
| Negative | π‘ Medium | [Error scenarios] |
| Security | π΄ High | [Only if authorization is affected] |
---
### 4. Test Data
| Category | Data | Purpose |
|-------------------|-----------|---------------------|
| Valid data | [example] | Happy path |
| Boundary values | [example] | Edge cases |
| Invalid data | [example] | Negative scenarios |
| Special cases | [example] | [Project-specific] |
---
### 5. Preconditions
- [ ] Environment is deployed and accessible
- [ ] Test data is prepared
- [ ] Required roles / accounts are created
- [ ] [Additional condition]
---
### 6. Acceptance Criteria
- [ ] All π΄ high-priority test cases pass
- [ ] Critical regression scenarios pass
- [ ] Negative scenarios return expected errors
- [ ] [Project-specific criterion]
---
### 7. Plan Risks
| Risk | Impact | Mitigation |
|----------|----------------------|----------------|
| [Risk 1] | High / Medium / Low | [How to reduce]|
| [Risk 2] | High / Medium / Low | [How to reduce]|
### 8. Checklist
| Check | Priority |
|-----------|-----------------------|
| [Check 1] | High / Medium / Low |
| [Check 2] | High / Medium / Low |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |