agentleFS
Sign inStart free
lucastosettolucastosetto/dev-skills/skills/qa-plan/SKILL.md

qa-plan

Skill0 starsChanged 24 days agoMITView on GitHub

Build a QA plan (automated unit/integration/E2E cases plus manual UI-first steps) from a spec, ticket, or the current branch's changes. Minimal by default; full BDD on request. Use on "write a QA plan", "test plan", "how should we test this", "/qa-plan", "/qa-plan full".

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow ../../shared/policy.md.

    line 12
  2. Very specific:

    When the UI does not exist yet or setup needs the API, write API steps and say why.

    line 48
  3. Very specific:

    Every acceptance criterion maps to at least one case.

    line 49

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

QA plan

Follow ../../shared/policy.md. Run dev-skills:project-profile if not loaded this session.

Inputs

The spec (spec.md) or context for the ticket if present; otherwise the current branch's diff against the base branch, plus the conversation. Look at how the project already tests similar code (test folders, factories/fixtures, E2E setup) so cases fit the existing suites.

Depth

  • minimal (default; also "smoke", "simple"): happy paths plus the few most likely edge cases.
  • full ("complete", "detailed"): every meaningful edge case, BDD style, with preconditions, steps, expected results and postconditions.

Write it

Save qa-plan.md next to the spec (or in the work folder for the branch).

# QA plan — <TICKET> <title> (<minimal|full>)

## Automated
| Tier | File / suite | Case | Covers |
|---|---|---|---|
| unit | `spec/models/foo_spec.rb` | rejects negative amount | AC2 |
| integration | ... | ... | ... |
| e2e | ... | ... | ... |

## Manual
### Setup
<data and accounts needed, through the UI where possible; API/console only when the UI cannot>
### Scenarios
1. <action> → <expected result>          (minimal)
   Given / When / Then                     (full)

## Out of scope

Manual steps are written for a QA engineer without deep engineering knowledge and target the UI. When the UI does not exist yet or setup needs the API, write API steps and say why. Every acceptance criterion maps to at least one case. The plan must be runnable by dev-skills:qa.

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