write-test-plan

write-test-plan is a skill for Claude Code from juliusz-cwiakalski/agentic-delivery-os. It costs 10 tokens per session (897 once invoked), scanned A, original, MIT.

A command that creates or updates a test plan for a proposed software change. It uses the change specification, implementation plan, and the project's testing rules to define what should be tested.

In plain words
What is it for?
Use it to plan backend, non-functional, or manual testing for a change identified by a work-item reference.
Why use it?
It helps prevent missed capabilities, interfaces, acceptance requirements, or test types before development begins.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions OpenCode.

Part of the ados plugin — 20 skills, 24 agents shipped together

Good fit Use it to plan backend, non-functional, or manual testing for a change identified by a work-item reference.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/juliusz-cwiakalski/agentic-delivery-os/write-test-plan
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add juliusz-cwiakalski/agentic-delivery-os --skill write-test-plan
Clone the repo
git clone --depth 1 https://github.com/juliusz-cwiakalski/agentic-delivery-os

Made for: Claude Code.

Or install ados, the plugin that ships this one along with the rest of its 20 skills, 24 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for write-test-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/juliusz-cwiakalski/agentic-delivery-os/write-test-plan/github.svg)](https://agentmods.dev/skills/juliusz-cwiakalski/agentic-delivery-os/write-test-plan)
Your own site
<a href="https://agentmods.dev/skills/juliusz-cwiakalski/agentic-delivery-os/write-test-plan"><img src="https://agentmods.dev/badge/skills/juliusz-cwiakalski/agentic-delivery-os/write-test-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for write-test-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/juliusz-cwiakalski/agentic-delivery-os/write-test-plan"><img src="https://agentmods.dev/badge/skills/juliusz-cwiakalski/agentic-delivery-os/write-test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 897 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 11
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00897
Opus 5 $0.00005 $0.00449
Sonnet 5 $0.00002 $0.00179
Haiku 4.5 $0.00001 $0.00090

Measured 12d ago against content hash 3fd91d3d4186, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

write-test-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.ados-claude/skills/write-test-plan/SKILL.md · 93 lines

What it actually says

User invocation: /write-test-plan <workItemRef> [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

<discovery_rules> Given workItemRef:

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

Files:

  • Spec: chg-<workItemRef>-spec.md
  • Plan: chg-<workItemRef>-plan.md
  • Test Plan: chg-<workItemRef>-test-plan.md
  • Branch: <change.type>/<workItemRef>/<slug> </discovery_rules>
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 93 lines · 10 tokens per session scan A 3fd91d3d4186

Subscribe to this mod's changes

write-test-plan is a skill published in the GitHub repository juliusz-cwiakalski/agentic-delivery-os (38 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 897 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

Verification & Quality Assurance

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

ruvnet/ruflo · 36 tokens

github-actions

Use when authoring or fixing GitHub Actions CI/CD — workflows under .github/workflows, triggers, job matrix, caching, token permissions, OIDC cloud deploys, environment gates, reusable workflows. NOT the Dockerfile or image build strategy (that is docker), NOT the branching model (that is git-workflow), NOT release…

ericrisco/rsc-harness · 81 tokens

ops-nuke-cicd

Designs and troubleshoots NUKE-based CI/CD pipelines for .NET services. Use when refactoring target graphs, splitting test flows, publishing reports, or diagnosing slow pipelines.

vasilyu1983/AI-Agents-public · 43 tokens

ai-agents-empirical-probe-toolkit

Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…

rjmurillo/ai-agents · 119 tokens

code-qualities-assessment

Assess code maintainability through 5 foundational qualities (cohesion, coupling, encapsulation, testability, non-redundancy) with quantifiable scoring rubrics. Works at method/class/module levels across multiple languages. Produces markdown reports with remediation guidance. Use when you ask to "assess…

rjmurillo/ai-agents · 108 tokens

ai-agents-portability-campaign

Execute cross-harness hook changes for Claude Code and GitHub Copilot CLI using the settled official contract, versioned probes, generators, and runtime tests. Use for run the portability campaign, port hooks to a new harness, copilot hook timeout regression, or new copilot cli release, recheck the contract. Do NOT…

rjmurillo/ai-agents · 104 tokens