manual-test
Skill9 starsChanged 3 months agoMITView on GitHub
Prepare for manual testing session with test plan based on known issues, recent changes, and acceptance criteria.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- sheshbabu/zentheir own version, first seen Nov 11, 2026
- hypequery/hypequerytheir own version, first seen Nov 8, 2026
- InfiniteRoomLabs/agent-opstheir own version, first seen Nov 1, 2026
- QAMarcos/claude-qa-flowtheir own version, first seen Nov 1, 2026
- kaeawc/auto-mobiletheir own version, first seen Oct 8, 2026
- tranquocthong/claude-spec-flowtheir own version, first seen Sep 22, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- sheshbabu/zen★ 1.2ksame name
- hypequery/hypequery★ 106same name
- kaeawc/auto-mobile★ 56same name
- QAMarcos/claude-qa-flow★ 12same name
- InfiniteRoomLabs/agent-ops★ 1same name
- tranquocthong/claude-spec-flow★ 0same name
- tranquocthong/spec-flow★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- .claude/agents/CLAUDE.mdCLAUDE.md
- .claude/hooks/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude/prompts/CLAUDE.mdCLAUDE.md
- .claude/rules/CLAUDE.mdCLAUDE.md
- .claude/skills/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- vision/CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- scaffold/llms.txtllms.txt
- architecture-checkSkill
- backlog-reviewSkill
- bootstrapSkill
- brainstormSkill
- buildSkill
- claude-sense-checkSkill
- code-qualitySkill
- commitSkill
- continueSkill
- custom-hooksSkill
- dashboardSkill
- debug-sessionSkill
- deploySkill
- discoverSkill
- doctorSkill
- fix-issueSkill
- framework-upgradeSkill
- handoffSkill
- help-meSkill
- ideateSkill
- lanesSkill
- merge-downSkill
- merge-upSkill
- optimizeSkill
- parallel-workSkill
- performance-checkSkill
- phase-reviewSkill
- pr-statusSkill
- quality-checkSkill
- quickstartSkill
- refine-loopSkill
- researchSkill
- retrospectiveSkill
- security-auditSkill
- skill-createSkill
- skill-evalSkill
- sprint-endSkill
- sprint-startSkill
- story-cycleSkill
- testing-cycleSkill
- test-validatorSkill
- UAT-cycleSkill
- undo-workSkill
- uninstallSkill
- weekly-maintenanceSkill
- wrap-upSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 7 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Read these files to understand what to test:
- Distinctive: line 34
Check the backlog for known gaps and bugs that are still TODO:
- Very specific: line 36
Read relevant epic files in docs/reference/backlog/
- Very specific: line 41
Read docs/progress.md for latest sprint info
- Very specific: line 42
Check docs/sprints/ for recent sprint specs with acceptance criteria
- Very specific: line 46
Read docs/testing/UAT_COVERAGE.md (if it exists) for test case status
- Very specific: line 51
Read docs/context/personas.md (if it exists) for lean persona cards — these provide CONTEXT, GOALS, FRUSTRATIONS, BEHAVIORS, EVALUATES BY, …
- Very specific: line 52
Read docs/reference/PRD_SUMMARY.md (if it exists) for success criteria and user flows
- Distinctive: line 55
If both personas.md and PRD Section 2 exist, prefer personas.md (richer behavioral detail for test generation)
- Distinctive: line 59
Before manual testing, verify the system is ready:
- Distinctive: line 61
Run the project's test command (from CLAUDE.md) to ensure automated tests pass.
- Distinctive: line 63
If pre-flight fails, fix issues before proceeding to manual testing.
- Distinctive: line 150
Do not proceed until user reports back.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
manual-test
Preparing manual test session...
1. Gather Context
Read these files to understand what to test:
Recent Changes
# What changed recently (last 20 commits or since last tag)
git log --oneline -20
git diff --stat HEAD~10Identify which areas of the project were modified and map to testable features.
Known Issues
Check the backlog for known gaps and bugs that are still TODO:
- Read relevant epic files in
docs/reference/backlog/ - These are confirmed issues — test around them but don't spend time re-discovering them
Recent Sprint Work
- Read
docs/progress.mdfor latest sprint info - Check
docs/sprints/for recent sprint specs with acceptance criteria
UAT Coverage
- Read
docs/testing/UAT_COVERAGE.md(if it exists) for test case status - Identify which areas have not been tested yet
Product Requirements & Personas
- Read
docs/context/personas.md(if it exists) for lean persona cards — these provide CONTEXT, GOALS, FRUSTRATIONS, BEHAVIORS, EVALUATES BY, and FAILURE LOOKS LIKE fields that directly inform exploratory testing in Phase 3C - Read
docs/reference/PRD_SUMMARY.md(if it exists) for success criteria and user flows - Section 3 (success criteria) identify what to prioritize testing
- Section 4 (user flows) provide the core scenarios to regression test
- If both personas.md and PRD Section 2 exist, prefer personas.md (richer behavioral detail for test generation)
2. Pre-Flight Checks
Before manual testing, verify the system is ready:
Run the project's test command (from CLAUDE.md) to ensure automated tests pass.
If pre-flight fails, fix issues before proceeding to manual testing.
3. Generate Test Plan
Generate a structured test plan covering three areas:
A. Regression Tests (from recent changes)
Based on the git diff, generate specific test scenarios for recently modified code:
#### Regression: [Area changed]
- [ ] **Scenario**: [What to test] — **Steps**: [How to test] — **Expected**: [What should happen]B. Known Issue Verification
For each recently fixed issue, generate a verification test:
#### Verify Fix: [Story ID] — [Title]
- [ ] [Specific step to verify the fix still works]For each open issue, note it as a known limitation:
#### Known Limitation: [Story ID] — [Title]
- Warning: [Brief description] — skip testing this areaC. Exploratory Testing
Based on architecture and project knowledge, suggest areas to probe.
If personas.md was loaded: Structure exploratory testing around each persona. For each persona, create scenarios that exercise their GOALS, probe their FRUSTRATIONS, use their CONTEXT constraints, and check for their FAILURE LOOKS LIKE scenarios. Apply their EVALUATES BY questions to each tested feature.
If only PRD_SUMMARY.md was loaded (no personas.md): Structure exploratory testing around each persona from PRD Section 2. For each persona, create scenarios that exercise their primary goal, pain points, and constraints.
Example: a persona with "low connectivity" context → test offline/slow-network behavior. A persona with "screen reader" context → test keyboard navigation and ARIA labels. A persona with "FAILURE LOOKS LIKE: gets stuck on jargon-filled error messages" → verify all error messages are plain English.
#### Exploratory: [Feature Area] (as [Persona Name])
- [ ] [Step 1 — what to do and what to look for, from persona's perspective]
- [ ] [Step 2]
#### Exploratory: Error Handling
- [ ] [Provoke an error condition and verify graceful handling]
#### Exploratory: Edge Cases
- [ ] [Test boundary conditions, empty states, large inputs]4. Present Test Plan
Output the complete test plan:
## Manual Test Plan — [Date]
### Environment
- [List required services, tools, and their status]
### A. Regression Tests ([count] scenarios)
[generated scenarios]
### B. Known Issue Checks
**Verified fixes**: [count]
**Known limitations**: [count]
[generated checks]
### C. Exploratory Testing ([count] areas)
[generated areas]
### How to Report Findings
Use `/testing-cycle <description of what you found>` for each issue.
This will classify it and handle it through the right process.
For structured UAT, use `/UAT-cycle <test-case-id>` to execute formal test cases.5. Wait for Testing
Tell the user:
The test plan is ready. Start the application if not already running, then work through the checklist. Report each finding with
/testing-cycle <feedback>. When done, wrap up with/sprint-end.
Do not proceed until user reports back.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

