Principle Outcome Oriented Execution

---
name: principle-outcome-oriented-execution
description: "Outcome-oriented execution. Apply when a planned rewrite or migration has explicit phase boundaries."
license: MIT
metadata:
  source: "pstack principle-outcome-oriented-execution, MIT, Copyright (c) 2026 Lauren Tan, github.com/cursor/plugins, adapted; checked against pstack 0.15.36 at commit 0bb6f37"
---

<!-- Generated by scripts/build.mjs from the sources; edit the source, then run npm run build. -->

# Outcome-oriented execution

Aim for the end state that you intend and can verify, not for smooth intermediate states.

**Why.** When each intermediate step must stay fully stable, you write temporary compatibility code, and it often becomes lasting debt. Move to the target architecture, and prove it correct at explicit verification boundaries.

**The rule.**
- Put the integrity of the end state before stability during the change.
- Breakage between phases is acceptable when it is planned, scoped and reversible.

**Guardrails.**
- Use this only for planned rewrites and migrations with explicit phase boundaries.
- Say where temporary breakage is acceptable.
- Keep strong checks on the areas that you change during the migration.
- At the end of the plan, run the full static and runtime verification.