Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

superplan-guard

Étoiles69

Forks2

Mis à jour28 mars 2026 à 17:26

Use when a fix or behavior change needs the smallest durable test, check, or proof so the contract will fail loudly if it regresses.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

superplan-md

superplan-md/superplan-plugin

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	superplan-guard
description	Use when a fix or behavior change needs the smallest durable test, check, or proof so the contract will fail loudly if it regresses.

Regression Guarding

Overview

Every important fix or behavior change should leave behind a guard.

Trigger

Use when:

a bug was fixed
a workflow contract changed
the agent asks "what test should protect this?"
a failure revealed a missing proof path

Core Rules

identify the exact behavior worth protecting
add the smallest credible guard that would fail before the bug returns
prefer the repo's existing test or verification style
guard the contract, not the incidental implementation
keep the guard close to the changed behavior when possible

Forbidden Behavior

adding broad noisy tests when one focused check would do
testing implementation trivia instead of user-visible or contract-visible behavior
skipping the guard because the fix feels obvious

Handoff

Likely follow-ons:

superplan-tdd when the guard should be written before the full fix
superplan-verify when the new guard becomes part of the proof path
superplan-postmortem when the missing guard revealed a broader process gap

Plus depuis ce dépôt

même dépôt

superplan-brainstorm

superplan-md/superplan-plugin

Use when routed repo work still has meaningful ambiguity about behavior, constraints, taste, or acceptance intent, and that ambiguity would make planning or execution unsafe.

2026-03-3169

superplan-entry

superplan-md/superplan-plugin

Use when a new request might involve repo work, tracked changes, workspace-specific decisions, or durable coordination and you must decide whether Superplan should engage before exploring or implementing.

2026-03-3169

superplan-execute

superplan-md/superplan-plugin

Use when tracked work is already shaped and the next move is to execute, verify, block, or request feedback without replanning from scratch.

2026-03-3169

superplan-plan

superplan-md/superplan-plugin

Use when the target is understood but the work still needs an execution path, task breakdown, or proof strategy before implementation begins.

2026-03-3169

superplan-route

superplan-md/superplan-plugin

Use when Superplan may engage and you need to decide whether to stay lightweight, create one tracked task, gather context first, or shape deeper structure before execution begins.

2026-03-3169

superplan-shape

superplan-md/superplan-plugin

Use when Superplan has decided to engage and the work still needs plans, specs, proof paths, or multiple tracked tasks shaped before bounded execution can start.

2026-03-3169

name	superplan-guard
description	Use when a fix or behavior change needs the smallest durable test, check, or proof so the contract will fail loudly if it regresses.

Regression Guarding

Overview

Every important fix or behavior change should leave behind a guard.

Trigger

Use when:

a bug was fixed
a workflow contract changed
the agent asks "what test should protect this?"
a failure revealed a missing proof path

Core Rules

identify the exact behavior worth protecting
add the smallest credible guard that would fail before the bug returns
prefer the repo's existing test or verification style
guard the contract, not the incidental implementation
keep the guard close to the changed behavior when possible

Forbidden Behavior

adding broad noisy tests when one focused check would do
testing implementation trivia instead of user-visible or contract-visible behavior
skipping the guard because the fix feels obvious

Handoff

Likely follow-ons:

superplan-tdd when the guard should be written before the full fix
superplan-verify when the new guard becomes part of the proof path
superplan-postmortem when the missing guard revealed a broader process gap