← LeaderboardThe Skill Leaderboard

principle-outcome-oriented-execution

Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.

Published by michael-denyer ↗michael-denyer/pstack-claude

Try your first task

principle-outcome-oriented-execution

Start a fresh conversation. Replace the highlighted placeholders.

Use principle-outcome-oriented-execution to plan the phased rewrite or migration of [system area] toward [target architecture], defining reversible temporary breakage and requiring full static and runtime verification at completion.

Required inputs

  • [system area]
  • [target architecture]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: principle-outcome-oriented-executiondescription: "Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code."user-invocable: false

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