Principle Outcome Oriented Execution
- 400 installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
When planning or executing a task, define the user-visible outcome first and trim steps that do not move measurable results closer to done.
About
Directs agents toward outcome-oriented execution: articulate the finished result upfront, choose actions that advance that result, ignore busywork that does not change user-visible value, and declare completion only when concrete acceptance criteria are satisfied.
- Start from desired end state
- Cut nonessential process steps
- Measure progress by results
- Align tasks to acceptance criteria
- Stop when outcome is met
Principle Outcome Oriented Execution by the numbers
- 400 all-time installs (skills.sh)
- Ranked #807 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill principle-outcome-oriented-executionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 400 |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
What it does
When planning or executing a task, define the user-visible outcome first and trim steps that do not move measurable results closer to done.
Files
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
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k