mcpField
P
principle-outcome-oriented-execution

principle-outcome-oriented-execution

github.com/backnotpropDevelopment3.1k5.7k installsUpdated today
Repository

About principle-outcome-oriented-execution

A development skill for planned rewrites and migrations that prioritizes a verifiable target architecture over keeping every intermediate state stable. It defines guardrails for scoped, reversible breakage and final verification.

Key features

  1. 01Prioritize the verified end state
  2. 02Allow scoped, reversible intermediate breakage
  3. 03Set explicit migration phase boundaries
  4. 04Run focused checks during migration
  5. 05Require full final verification

Use cases

  1. 01Plan a major rewrite
  2. 02Migrate between architectures
  3. 03Set verification criteria for staged changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/backnotprop/pstack --skill principle-outcome-oriented-execution

After installing, type/principle-outcome-oriented-executionin Claude Code to confirm it loaded.

Details

From the project README

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

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