# Principle Outcome Oriented Execution

Apply during planned rewrites and migrations with explicit phase boundaries.

- Repository: https://github.com/nightly-labs/openbot (4509 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nightly-labs/openbot --skill principle-outcome-oriented-execution -g -a claude-code -y`
Codex: `npx skills add nightly-labs/openbot --skill principle-outcome-oriented-execution -g -a codex -y`
Cursor: `npx skills add nightly-labs/openbot --skill principle-outcome-oriented-execution -g -a cursor -y`
Gemini CLI: `npx skills add nightly-labs/openbot --skill principle-outcome-oriented-execution -g -a gemini-cli -y`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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