agentleFS
Sign inStart free
evgenii-studitskikhevgenii-studitskikh/Claude-Code-SaaS-Studio/.claude/skills/qa-plan/SKILL.md

qa-plan

Skill1 starsChanged 5 months agoMITView on GitHub

Define the test strategy and tooling for the SaaS app before writing tests: the test pyramid, what to cover at each layer, and the security-critical seams. Run after the first feature exists. Produces a qa-plan doc.

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

Create a free account to mount
Files
SKILL.md

Decide how this SaaS will be tested before scaffolding or writing any tests. Non-autonomous: ask first, present options, get sign-off.

Phases

  1. Load context — read docs/specs/prd.md, docs/specs/architecture.md, and docs/specs/data-model.md if present, to learn the features and the tenant model. If the PRD is missing, stop and direct to /write-prd.
  2. Choose the pyramid — propose how much unit vs. integration vs. e2e, and the tools (Vitest + Testing Library, Playwright, Stripe-signed test payloads, Supabase RLS tests). Present 2–3 options with trade-offs.
  3. Identify critical seams — list the must-test risk areas: tenant isolation (RLS), auth/session, billing webhooks, input validation boundaries.
  4. Draft the plan — fill .claude/templates/qa-plan.md into docs/specs/qa-plan.md (draft, await approval). Honor the review intensity: under full, confirm each section; under lean, one confirmation before writing; under solo, write then summarize.
  5. Next step — on approval, point to /test-setup.

Output

docs/specs/qa-plan.md. Writes nothing else without approval.

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