agentleFS
Sign inStart free
danielvm-gitdanielvm-git/bigpowers/skills/plan-tests/SKILL.md

plan-tests

Skill288 starsChanged 5 days agoMITView on GitHub

Design a risk-scaled test architecture for an epic before implementation begins. Produces prioritized scenarios, test level distribution, and fixture plans based on TEA and bigpowers principles.

3 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    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:

    Read specs/epics/eNN-*/ story list.

    line 15
  2. Distinctive:

    Analyze Epic: Read sliced stories in the active epic capsule.

    line 18
  3. Distinctive:

    DO NOT: write test code or production code during this skill.

    line 26
  4. Distinctive:

    Default to pushing tests to the lowest possible level.

    line 29

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

Plan Tests

Spine position: Between slice-tasks and plan-work for epics with risk: P0|P1. Optional (can be waived in state.yaml) for P2/P3.

Bridges the gap between slicing and planning by systematically designing the test suite as a first-class system. Produces specs/tech-architecture/eNN-TEST_PLAN_LATEST.md.

Pre-flight

  • Read specs/epics/eNN-*/ story list.

Core Workflow

  1. Analyze Epic: Read sliced stories in the active epic capsule.
  2. Risk Assessment: Map behaviors to P0–P3 risk tiers.
  3. Level Strategy: Classify each scenario (Unit, Integration, E2E).
  4. Fixture Design: Plan factories, network intercepts, mocks (see REFERENCE.md).
  5. NFR Plan: Define verifiable commands for Non-Functional Requirements. Skip if --lite.
  6. Publish: Generate specs/tech-architecture/eNN-TEST_PLAN_LATEST.md.

Hard Gates & Guardrails

  • DO NOT write test code or production code during this skill.
  • Scenario ID format MUST be: SC-eNNsYY-P{0|1|2|3}-NN.
  • plan-work MUST reference these scenario IDs in its §17 Gherkin acceptance criteria.
  • Default to pushing tests to the lowest possible level.

Execution Modes

  • $bmad plan-tests: Standard execution.
  • $bmad plan-tests --lite: Skips NFRs and complex fixture planning.

Verify

→ verify: test -f specs/tech-architecture/e32-TEST_PLAN_LATEST.md

Handoff

Gate: READY -> next: plan-work Writes: state.yaml handoff.next_skill = plan-work

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