P
principle-outcome-oriented-execution
About principle-outcome-oriented-execution
A skill for planning rewrites and migrations around a verifiable target state rather than preserving every intermediate state. It is intended for work with explicit phases, scoped temporary breakage, and final static and runtime checks.
Key features
- 01Prioritizes target-state integrity
- 02Allows planned, reversible intermediate breakage
- 03Defines migration phase boundaries
- 04Requires final static and runtime checks
Use cases
- 01Planning a rewrite with temporary compatibility breaks
- 02Migrating architecture in explicit phases
- 03Verifying completion of a migration
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/principle-outcome-oriented-executionin Claude Code to confirm it loaded.
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
Comments
Markdown supported