agentleFS
joris887joris887/exosuit/.claude/skills/manual-test/SKILL.md

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

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
  1. Distinctive:

    Read these files to understand what to test:

    line 20
  2. Distinctive:

    Check the backlog for known gaps and bugs that are still TODO:

    line 34
  3. Very specific:

    Read relevant epic files in docs/reference/backlog/

    line 36
  4. Very specific:

    Read docs/progress.md for latest sprint info

    line 41
  5. Very specific:

    Check docs/sprints/ for recent sprint specs with acceptance criteria

    line 42
  6. Very specific:

    Read docs/testing/UAT_COVERAGE.md (if it exists) for test case status

    line 46
  7. Very specific:

    Read docs/context/personas.md (if it exists) for lean persona cards — these provide CONTEXT, GOALS, FRUSTRATIONS, BEHAVIORS, EVALUATES BY, …

    line 51
  8. Very specific:

    Read docs/reference/PRD_SUMMARY.md (if it exists) for success criteria and user flows

    line 52
  9. Distinctive:

    If both personas.md and PRD Section 2 exist, prefer personas.md (richer behavioral detail for test generation)

    line 55
  10. Distinctive:

    Before manual testing, verify the system is ready:

    line 59
  11. Distinctive:

    Run the project's test command (from CLAUDE.md) to ensure automated tests pass.

    line 61
  12. Distinctive:

    If pre-flight fails, fix issues before proceeding to manual testing.

    line 63
  13. Distinctive:

    Do not proceed until user reports back.

    line 150

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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~10

Identify 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.md for 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 area

C. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.