agentleFS
Sign inStart free
MyriambsMyriambs/argus-qa/skills/qa-plan/SKILL.md

qa-plan

Skill0 starsChanged 28 days agoMITView on GitHub

Create a risk-based test plan for a feature, story, PRD, ticket or release — including a requirement review (ambiguities, missing acceptance criteria, questions for the PO) and a risk map that decides where testing effort goes.

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

1 rule. 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    When it returns, show the user: the summary, the requirement-review questions (they're the highest-value output, so put them first), and …

    line 14

“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

Delegate to the qa-architect subagent (it may appear as argus-qa:qa-architect).

Brief it with:

  • Input: $ARGUMENTS. If this is a file path, issue number (gh issue view) or URL, tell the agent to read it. If it's empty, ask the user what to plan for.
  • The relevant facts from .qa/context.md (if it exists).
  • Deliverable: its standard Test Plan format, saved to .qa/reports/test-plan-<slug>.md.

When it returns, show the user: the summary, the requirement-review questions (they're the highest-value output, so put them first), and the top 5 risks. Then offer /qa-cases to turn the plan into test cases.

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