Apply whenever a change threads a new required value through existing callers, not just named rewrites/migrations — a new required field, a new parameter, a new required IPC/API argument. Converge on the target shape in one slice; don't preserve smooth intermediate states with throwaway compatibility code.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Outcome-Oriented Execution
Optimize for the intended, verifiable end state rather than preserving smooth intermediate states.
**Why:** Keeping every intermediate step fully stable often creates temporary compatibility code that becomes long-lived debt. Converge on the target architecture and prove correctness at explicit verification boundaries.
**Core rule:**
- Prioritize end-state integrity over transitional stability
- Intermediate breakage is acceptable when it is planned, scoped, and reversible
- Always run final verification before declaring done
**Guardrails:**
- Use this for planned rewrites and migrations with explicit phase boundaries — and for small changes too: a new required field, a new IPC argument, a new parameter threaded through a pipe are migrations at small scale, not exceptions
- Declare where temporary breakage is acceptable
- Keep high-signal checks for actively touched areas while migrating
- Require full static and runtime verification at plan completion
…
The line at the top of this page pins the label git:20260825.847374d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_gvg6kgpse7j4ezp5
GET https://markdownregistry.com/api/v1/resolve?ref=edbertchan/catstack/principle-outcome-oriented-execution
GET https://markdownregistry.com/api/v1/blob/2c9260217037ad5e260b59f0c248351a57f4b12dc604d26f3a87a53fe8c4ca1b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
edbertchan/catstack · corpus/skills/cat-mode/SKILL.md · Edbert's personal working conventions, mined from real session history across his projects. Use when Edbert asks to…
edbertchan/catstack · corpus/skills/principle-assert-invariants-not-last-bug/SKILL.md · Apply after a bug ships past review or a passing grade/check: assert the general class of failure instead of patching…
edbertchan/catstack · corpus/skills/principle-bind-to-named-inventory/SKILL.md · Apply after an audit, scoring review, or a request for a "real classifier" / "less arbitrary weights" when existing…
edbertchan/catstack · corpus/skills/principle-build-the-lever/SKILL.md · Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or…
edbertchan/catstack · corpus/skills/principle-encode-lessons-in-structure/SKILL.md · Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the…
edbertchan/catstack · corpus/skills/principle-experience-first/SKILL.md · Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship…
edbertchan/catstack · corpus/skills/principle-fix-root-causes/SKILL.md · Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach…
edbertchan/catstack · corpus/skills/principle-flag-your-own-corrections/SKILL.md · Apply whenever you are about to admit fault in any wording — a fact, number, claim, or check you already stated turns…
edbertchan/catstack · corpus/skills/principle-generalize-from-rejection/SKILL.md · Apply when a mechanical gate — a lint, validator, blocked-command guard, or CI check — rejects your output for the same…
cursor/plugins · pstack/skills/principle-outcome-oriented-execution/SKILL.md · Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
cursor/plugins · harness/pstack/claude-code/skills/principle-outcome-oriented-execution/SKILL.md · Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
michael-denyer/pstack-claude · plugins/pstack/skills/principle-outcome-oriented-execution/SKILL.md · Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
backnotprop/pstack · skills/principle-outcome-oriented-execution/SKILL.md · Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
j-star-films-studios/vibecode-protocol-suite · assets/.agent/skills/engineering-principles/outcome-oriented-execution/SKILL.md · Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
creedants/pstack-t3 · skills/principle-outcome-oriented-execution/SKILL.md · Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
arjitj2/open-pstack · plugins/pstack/skills/principle-outcome-oriented-execution/SKILL.md · Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
painhardcore/pstack · .opencode/skills/principle-outcome-oriented-execution/SKILL.md · Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't…
