skills.rest
jeremybrasher
jeremybrasherCOMMUNITY
Explore all skills by this author →
GitHub

principle-outcome-oriented-execution

Guides planned rewrites and migrations toward target architecture with explicit verification boundaries.

Updated Aug 28, 2026
Search Tags:#refactoring#verification#migration#technical debt#software architecture#engineering principles#rewrite
One-click install
npx skills add https://github.com/jeremybrasher/grokbot-skills --skill principle-outcome-oriented-execution-jeremybrasher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-outcome-oriented-execution
Source: https://github.com/jeremybrasher/grokbot-skills/tree/main/collections/pstack/skills/principle-outcome-oriented-execution
Command: npx skills add https://github.com/jeremybrasher/grokbot-skills --skill principle-outcome-oriented-execution-jeremybrasher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planned rewrites and migrations often accumulate throwaway compatibility code because teams try to keep every intermediate state stable. This Skill helps you converge on the target architecture instead, accepting planned, scoped, and reversible intermediate breakage while requiring full verification at completion. ## Core Features & Use Cases - End-state prioritization: Optimizes for the intended, verifiable end state rather than preserving smooth intermediate states during rewrites. - Structured intake and HOLD gates: Stops and reports missing inputs (situation, trigger evidence, decision to change) instead of guessing or citing the principle decoratively. - Cut-first defaults: Prefers the smallest structural change, deleting before adding, and refuses scope expansion without evidence. - Use Case: During a multi-phase migration from a legacy module to a new service, apply this Skill to declare where temporary breakage is acceptable, keep high-signal checks on touched areas, and require full static and runtime verification before declaring the migration done. ## Quick Start Apply the outcome-oriented execution principle to my planned migration plan and tell me which intermediate compatibility code I should cut and where verification boundaries belong.

Frequently Asked Questions about principle-outcome-oriented-execution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle intermediate breakage during a large code migration?▼

Accept intermediate breakage when it is planned, scoped, and reversible. Declare upfront where temporary breakage is acceptable, keep high-signal checks on actively touched areas, and require full static and runtime verification at plan completion.

When should I prioritize end-state over transitional stability in a rewrite?▼

Prioritize the end state during planned rewrites and migrations with explicit phase boundaries. Keeping every intermediate step stable creates temporary compatibility code that becomes long-lived debt, so converge on the target architecture and prove correctness at verification boundaries.

When should I not use outcome-oriented execution?▼

Do not use it when the trigger is not met, when a narrower operational skill covers the same decision, or when you would only cite the principle without changing a choice. It is also unsuited to work lacking explicit phase boundaries.

What happens when required inputs for applying this principle are missing?▼

The Skill returns a HOLD instead of guessing. It names what is missing, such as the situation object or trigger evidence, and states what is needed before proceeding, treating the HOLD as a return value rather than a delay.

Does this approach allow deleting code before adding replacements?▼

Yes, it defaults to cutting first. If the principle says delete, delete before adding, prefer the smallest structural change, and expand scope only with evidence from the request or the observed system.

Related Skills

Explore More Software Engineering Skills→
FlyFissionFlyFission
33

questioning-attitude

Restate a change as a decision question and document assumptions and evidence gaps.

Community
Advanced
mmdmcymmdmcy

principle-outcome-oriented-execution

Guides planned rewrites and migrations toward target architecture without throwaway compatibility code.

Community
Basic
cursorcursor
6.6k

principle-outcome-oriented-execution

Guides planned rewrites and migrations toward target architecture with explicit verification boundaries.

Official
Basic
herdiansahherdiansah
23

code-refactoring

Refactor legacy codebases and migrate outdated frameworks using the Strangler Fig pattern.

Community
Advanced