Agent skill · software engineering · cursor
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.
Why this skill is useful
Codifies a structured approach to managing rewrites and migrations, preventing the AI from guessing how to handle transitional states.
What it needs
About 1k tokens when loaded. Last updated 2026-08-06. 2,555 stars on the source repository.
What this skill does
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
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills cursor/principle-outcome-oriented-execution