execute

Execute chosen solutions with pre-flight checks, incremental builds, drift detection, and salvage handling.

3|Updated Jan 27, 2026

Search Tags:#build #drift-detection #preflight #execute #session-persistence #salvage

Ready to run

npx skills add https://github.com/open-horizon-labs/skills --skill execute-open-horizon-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/open-horizon-labs/skills/tree/main/execute
Command: npx skills add https://github.com/open-horizon-labs/skills --skill execute-open-horizon-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes the chosen solution by coordinating pre-flight checks, building, monitoring drift, and salvaging as needed, bridging the gap from solution space to a shipped outcome.

Core Features & Use Cases

Pre-flight checks verify aim clarity, constraints, context, scope, and success criteria before coding.
Build & Verify perform the work in small, testable increments with proper change management.
Drift detection continuously compare current work against the original aim and decide on salvage if divergence occurs.
Salvage & restart extract learning and restart with corrected scope or aim to maintain progress.
Session persistence optionally records execution context to .oh session files to support long-running workflows and cross-skill handoffs.

Quick Start

Invoke /execute when your aim is clear, the solution is chosen, and you are ready to implement.

Frequently Asked Questions about execute

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

FAQPage Schema

How do I automate end-to-end execution from a chosen solution to shipped code?▼

Bridging execution from plan to shipped code involves automating pre-flight validation, incremental building, drift detection, and salvage handling. You initiate this by invoking execute once your aim is clear, a solution is chosen, and context is loaded.

What are pre-flight checks in software execution and why do I need them?▼

Pre-flight checks validate aim clarity, constraints, context, scope, and success criteria before coding starts. They ensure the selected solution is fully scoped and ready for incremental building and delivery.

How do I handle drift detection during incremental software building?▼

Drift detection during incremental building continuously compares current work against the original aim. If divergence occurs, it triggers salvage to extract learning and restart with a corrected scope or aim to maintain progress.

Can I persist execution context for long-running workflows across different skills?▼

Yes, you can persist execution context for long-running workflows using session persistence. It optionally records execution context to .oh session files to support cross-skill handoffs and maintain continuous state.

What is the best way to salvage a software build when scope diverges from the original aim?▼

The best way to salvage a software build when scope diverges is to extract learning from the current drift and restart with a corrected scope or aim. This maintains progress while ensuring the final shipped code aligns with requirements.

What do I need to set up before starting automated solution execution?▼

Before starting automated solution execution, you need a clear aim, a chosen solution, and loaded context. These prerequisites satisfy the pre-flight validation requirements for scope, constraints, and success criteria.