principle-outcome-oriented-execution
About principle-outcome-oriented-execution
A development skill for planned rewrites and migrations that prioritizes a verified target state over stability at every intermediate step. It defines guardrails for scoped breakage and requires full static and runtime verification at completion.
Key features
- 01Prioritize verified end-state integrity
- 02Allow planned, scoped intermediate breakage
- 03Define explicit migration phase boundaries
- 04Keep focused checks on active areas
- 05Require final static and runtime verification
Use cases
- 01Planning a multi-phase rewrite
- 02Migrating architecture with temporary breakage
- 03Defining verification gates for a migration
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ mdsmithaustin/ pstack --skill principle-outcome-oriented-executionAfter installing, type/principle-outcome-oriented-executionin Claude Code to confirm it loaded.
Bundled filesagents/openai.yaml
Details
From the project READMEOutcome-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
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