output-contractslisted
Install: claude install-skill RICK-ORPHEN/agent-discipline-skills
# Output Contracts — the standard for what may ship
This skill ships **criteria, not procedures.** Other skills read it to decide pass or fail.
## What is in here
| File | Applies to | Contents |
|---|---|---|
| `work-contract.yaml` | Documents, decks, reports, sites, landing pages, dashboards | Forbidden destructive commands, per-archetype acceptance criteria, ban on silent degradation |
This is a starting point, not a finished policy. **Adapt the archetypes and the acceptance
criteria to your own deliverables.** What must not change is the three-valued verdict, the ban
on silent degradation, and never counting an unchecked item as a pass.
## Three gates
1. **Entry** — run preflight once before touching any source material or external tool. If a prerequisite is
missing, **stop; do not try to fix the environment on the spot.** Reinstalling a missing
tool mid-run has broken things that were already working.
2. **Mid-work** — do not run operations you cannot undo: `brew uninstall`, `pip uninstall`,
`rm -rf <system path>`, `git push --force`, `git add -A`, `DROP TABLE`. The rule is
*install the new thing, verify it, then remove the old one.* When a command is
borderline, check it against `irreversible_ops.block_patterns` in the contract.
3. **Exit** — check the output acceptance criteria before handing anything over and return
one of three verdicts: **PASS / DEGRADED / FAIL**.
## ⚠️ DEGRADED is not success
Any workaround that **changes the nature of the