P
principle-outcome-oriented-execution
About principle-outcome-oriented-execution
A development skill for planned rewrites and migrations that prioritizes a verifiable target state over uninterrupted intermediate stability. It defines when temporary breakage is acceptable and requires checks at migration milestones and completion.
Key features
- 01Prioritize the target state
- 02Allow scoped, reversible breakage
- 03Set migration phase boundaries
- 04Verify touched areas during migration
- 05Run full checks at completion
Use cases
- 01Planning a major rewrite
- 02Migrating between architectures
- 03Defining acceptable breakage windows
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