AgentStack
SKILL verified MIT Self-run

Write Test Plan

skill-juliusz-cwiakalski-agentic-delivery-os-write-test-plan · by juliusz-cwiakalski

Generate or update change test plan

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-juliusz-cwiakalski-agentic-delivery-os-write-test-plan

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Write Test Plan? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Create or update a COMPLETE, requirements-driven TEST PLAN for a change.

User invocation: /write-test-plan [options]

Options: focus=backend, nfr-only, no-manual, etc.

The TEST PLAN:

  • Ensures full coverage of capabilities, interfaces, and acceptance criteria
  • Aligns with implementation plan phases
  • Maps scenarios to test types per .ai/rules/testing-strategy.md

$ARGUMENTS

  • workItemRef = first token matching pattern - (e.g., PDEV-123, GH-456)
  • Remaining args = options (e.g., focus=backend)
  • If no valid workItemRef found, output NEEDS_INPUT:

`` NEEDS_INPUT: workItemRef required Usage: /write-test-plan [options] Example: /write-test-plan PDEV-123 focus=backend ``

Given workItemRef:

  1. Search for folder: doc/changes/**/*----*/
  2. Locate spec: chg--spec.md (required)
  3. Locate plan: chg--plan.md (optional)
  4. Read: .ai/rules/testing-strategy.md (required)

Files:

  • Spec: chg--spec.md
  • Plan: chg--plan.md
  • Test Plan: chg--test-plan.md
  • Branch: //
  1. Parse workItemRef and options from $ARGUMENTS
  2. Locate change folder, spec, plan per
  3. Read .ai/rules/testing-strategy.md; FAIL if missing
  4. Extract F-#, AC-#, API-#, NFR-# from spec
  5. Checkout/create branch
  6. Delegate to @test-plan-writer agent (it has full template and rules)
  7. Report: path to created test plan, next step: /run-plan

After successful execution:

  • Created/updated file path
  • Branch name
  • Coverage summary (how many AC-# covered, any TODOs)
  • Recommendation: "Run /run-plan to begin execution"
  • Spec must exist; fail if not found
  • Testing strategy must exist; fail if not found
  • Only the test plan file may be written
  • Derive all context from spec/plan; do not invent requirements
  • Mark uncovered AC-# as TODO with open questions

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.