Cursor Skill

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.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download backnotprop-pstack-skills_principle-outcome-oriented-execution-ecec42a.zip · 0 KB

Install

skills CLI npx skills add https://github.com/backnotprop/pstack/tree/main/skills/principle-outcome-oriented-execution
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install backnotprop-pstack@llmmart
Git git clone https://github.com/backnotprop/pstack.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole backnotprop/pstack collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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
Files (pstack)
  • SKILL.md 1.1 KB
    ---
    name: principle-outcome-oriented-execution
    description: "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."
    disable-model-invocation: true
    ---
    
    # 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
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.