Skip to content

unxed/f4 / .agents/skills/aif-qa

aif-qa

Verified

QA workflow for testing a feature or task implementation. Analyzes changes, produces test plans, and describes concrete test scenarios. Use when user says "test this", "write test plan", "what should I test", or "QA this branch".

FileKindSize
SKILL.mdskill md11.9 KB
references/CHANGE-SUMMARY.mdmarkdown9.8 KB
references/TEST-CASES.mdmarkdown4.1 KB
references/TEST-PLAN.mdmarkdown3.8 KB
templates/CHANGE-SUMMARY.mdmarkdown1.1 KB
templates/TEST-CASES.mdmarkdown680 B
templates/TEST-PLAN.mdmarkdown2.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   |
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall