Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; 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
- 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:20260827.04830a9, 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_iyidoozwosic2izp
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/principle-outcome-oriented-execution
GET https://markdownregistry.com/api/v1/blob/f2fe80adf2da1e1e15aa1d1b465f1cb963acb05114be9032a89ae6ead06df288
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.
painhardcore/pstack · .opencode/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…
painhardcore/pstack · .opencode/skills/arena/SKILL.md · Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for…
painhardcore/pstack · .opencode/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
painhardcore/pstack · .opencode/skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives your app the way a user does — any language, framework, or…
painhardcore/pstack · .opencode/skills/figure-it-out/SKILL.md · Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a…
painhardcore/pstack · .opencode/skills/how/SKILL.md · Explain how a subsystem works, trace a runtime flow, or determine where code and ownership belong before making a…
painhardcore/pstack · .opencode/skills/interrogate/SKILL.md · Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find…
painhardcore/pstack · .opencode/skills/principle-boundary-discipline/SKILL.md · Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI…
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…
edbertchan/catstack · corpus/skills/principle-outcome-oriented-execution/SKILL.md · Apply whenever a change threads a new required value through existing callers, not just named rewrites/migrations — a…
