agentleFS
Sign inStart free
sarveshtalelesarveshtalele/devcrew/.claude/skills/test-plan/SKILL.md

test-plan

Skill1 starsChanged 3 months agoMITView on GitHub

Build an IEEE 29119 test plan for an epic and split it into concrete unit, integration, and E2E tasks. Use at the start of stage 7, or during stage 4 to define test hooks early.

17 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test plan for: $ARGUMENTS

    line 6
  2. Very specific:

    Method: Follow User-Story-Testing.md — story format, Given/When/Then criteria, level assignment, naming, and the Definition of Ready/Done …

    line 10
  3. Very specific:

    Trace first: Every REQ-### gets at least one test ID.

    line 11

“Common” is measured: kept by at least 6 in 10 of the 14 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

Test plan for: $ARGUMENTS

Output docs/design/test-plan-<epic>.md from templates/test-plan.md.

  1. Method. Follow User-Story-Testing.md — story format, Given/When/Then criteria, level assignment, naming, and the Definition of Ready/Done checklists.
  2. Trace first. Every REQ-### gets at least one test ID. A requirement with no test is not a requirement, it is a hope. Update docs/prd/traceability.md.
  3. Assign the level (ISTQB) per requirement — unit / integration / system(E2E). Push tests down: if it can be a unit test, it must not be an E2E test.
  4. Unit (qa-engineer): boundaries — empty, one, many, max, max+1, null, wrong type, unicode, negative, zero, duplicate, concurrent, expired, unauthorized, malformed. ≥85% of changed lines.
  5. Integration (qa-engineer): real Postgres/Redis via testcontainers, real HTTP layer. Never mock the thing under test.
  6. E2E (e2e-automation): journeys only, plus one failure path. Role-based locators, zero fixed waits, self-seeded data.
  7. A11y: axe scan per page state, keyboard journey with visible focus and focus trapping, at 375/768/1280. Zero violations.
  8. Security cases: authz bypass as another user, injection payloads, oversized input, missing/invalid auth, rate limit, and assertions that PII/PHI/CHD appear in neither logs nor error bodies.
  9. Exit criteria: coverage met, zero flakes in 3 consecutive runs, all Critical/High defects closed.
  10. File each item as a card in trackers/qa.md or trackers/e2e.md.

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.

Check your setup, free