mcpField
P
principle-outcome-oriented-execution

principle-outcome-oriented-execution

github.com/q-qp-pDevelopment149 installsUpdated 3w ago
Repository

About principle-outcome-oriented-execution

A planning skill for rewrites and migrations that prioritizes a verified target state over uninterrupted stability at every intermediate step. It defines guardrails for scoped, reversible breakage and verification at phase boundaries.

Key features

  1. 01Prioritizes target-state integrity
  2. 02Allows scoped intermediate breakage
  3. 03Defines migration phase boundaries
  4. 04Requires focused checks during migration
  5. 05Requires full verification at completion

Use cases

  1. 01Planning a codebase rewrite
  2. 02Managing a phased migration
  3. 03Defining checks for migration completion

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/q-qp-p/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