SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Community / AGENT SKILL
principle-outcome-oriented-execution
0
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.
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
# 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 - Always run final verification before declaring done **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