/

/test-plan

746

Produce a focused test plan for a change. Use when the user asks how to test a feature, what cases to cover, or for a QA checklist before shipping.

Ask your Agent

Use this Skill: https://skilld.dev/gh/cloudflare/agents/test-plan

This session only. Nothing lands on disk.

SKILL.md

≈40 tokens always: the name and description. ≈190 when used: this file.

Turn a change description into a short, prioritized test plan.

Restate what changed in one sentence.
Identify the riskiest behaviors first (data loss, auth, money, concurrency).
List concrete test cases as given / when / then, happy paths first, then edge cases and failure modes.
Note any setup, fixtures, or environment the cases need.
Call out what is explicitly out of scope so the plan stays focused.

## Risks

- Ranked list of the riskiest areas.

## Cases

1. given … / when … / then …

## Out of scope

- Anything intentionally not covered.

Keep the plan small enough to act on immediately. If the change is unclear, ask for the acceptance criteria before listing cases.

No alerts3mo3 checks · Risk SAFE

Gen Agent Trust Hub3mo
This skill provides a structured framework for generating software test plans based on user input. It is purely instructional and does not contain any code, external dependencies, or network-enabled operations.
Socket3mo
No alerts
Snyk3mo
Risk: LOW · No issues

Signed by skilld at 87006e2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 18 hours ago.

Activeupdated 4 months ago