mcpField
P
principle-outcome-oriented-execution

principle-outcome-oriented-execution

github.com/hachejDevelopment160 installsUpdated 1d ago
Repository

About principle-outcome-oriented-execution

A development skill for planned rewrites and migrations that prioritizes a verifiable target state over uninterrupted stability during every intermediate step. It defines guardrails for scoped breakage and verification at completion.

Key features

  1. 01Prioritize target-state integrity
  2. 02Allow planned, reversible breakage
  3. 03Set migration phase boundaries
  4. 04Verify touched areas during migration
  5. 05Run full checks at completion

Use cases

  1. 01Planning a rewrite with temporary incompatibilities
  2. 02Migrating architecture in explicit phases
  3. 03Checking migration correctness at completion

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/hachej/boring-stack --skill principle-outcome-oriented-execution

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

Bundled filesLICENSE

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