Skip to content

minwoo19930301/decant / plugins/decant/skills/decant-spec

decant-spec

Verified

Turn an ambiguous or high-impact change request into a small executable specification using async questions and a confirmed task contract. Use when scope, authority, acceptance checks, or rollback are unclear, or when the user asks for async questions and says not to stop; do not use for a narrow reversible edit or a question the repository can answer.

FileKindSize
SKILL.mdskill md4.4 KB
agents/openai.yamlconfig259 B
evals/cases.jsonconfig3.1 KB
references/task-contract.mdmarkdown1.8 KB

references/task-contract.md

View on GitHub
# Confirmed Task Contract

Use this compact contract after any necessary clarification. Keep it in the
conversation unless the user or repository workflow requests a file artifact.

```yaml
status: confirmed | unresolved
revision: 1
supersedes: null
goal: one observable user outcome
non_goals:
  - behavior intentionally outside this change
constraints:
  - technical, provider, platform, policy, or licensing boundary
allowed_mutations:
  - files, systems, or external actions the request authorizes
forbidden_actions:
  - publication, destructive work, or scope expansion not authorized
acceptance_checks:
  - observable pass condition and its evidence
verification:
  - exact deterministic check or review method
rollback: smallest safe revert path
decisions:
  - statement: material premise used by the plan
    source: user_decision | repo_fact | safe_assumption | blocker
    evidence: answer, file, command result, or named owner
unresolved:
  - remaining blocker; empty only when status is confirmed
```

## Confirmation rules

- A specific original request may confirm revision 1 without a redundant
  question when evidence does not expose a material choice.
- A reversible choice uses async question mode: state the question and the
  assumption, record `safe_assumption`, and continue. Do not wait.
- If the choice is irreversible — deployment, production data, deletion,
  sending, push, a pull request, public posting, or a large spend — restate
  the contract and wait for confirmation before that action.
- `status: unresolved`, a `blocker` decision, or a non-empty material
  `unresolved` list prevents a build handoff.
- A material change creates revision N+1 and sets `supersedes` to the prior
  revision. Preserve the earlier contract instead of rewriting its history.
- The contract records intent; it is not proof that implementation or
  verification succeeded.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall