Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

test-plan

Sterne5.248

Forks623

Aktualisiert29. Mai 2026 um 11:44

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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

cloudflare

cloudflare/agents

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	test-plan
description	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.

Test Plan

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

Process

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.

Output format

## 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.

Mehr aus diesem Repository

gleiches Repository

open-pr

cloudflare/agents

Take a cloudflare/agents GitHub issue plus any repro findings and one-shot a fix PR — branch, change, test, push, and open the PR linked to the issue.

2026-07-085.2k

reproduce

cloudflare/agents

Reproduce a cloudflare/agents GitHub issue by scaffolding a minimal Agents/Worker project and deploying it to a temporary Cloudflare account, then report findings back on the issue.

2026-07-085.2k

code-review

cloudflare/agents

Review code changes for correctness, clarity, and risk. Use when the user asks for a review, a second opinion on a diff, or feedback on code they wrote.

2026-06-075.2k

escalation

cloudflare/agents

Decide when and how to escalate a customer conversation to a human agent. Use when a request is high-risk, the customer is frustrated, or the issue is outside what you can resolve.

2026-06-075.2k

workspace-digest

cloudflare/agents

Summarize the files saved in this assistant's shared workspace. Use when the user asks what is in their workspace, for a file inventory, or a digest of saved work.

2026-06-075.2k

debug-plan

cloudflare/agents

Create a systematic debugging plan for a bug report. Use when the user asks how to investigate a failure, regression, or unexpected behavior.

2026-05-295.2k

name	test-plan
description	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.

Test Plan

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

Process

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.

Output format

## 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.