execute
/execute
Bridge from Solution Space to shipped code. Pre-flight, build, detect drift, salvage if needed.
Execute sits within Intent → Execution → Review. It contains an inner loop: build, check alignment, course-correct or salvage.
When to Use
Invoke /execute when aim is clear, solution is chosen, context is loaded, and you're ready to build.
Do not use when: Aim is unclear (/aim), still exploring (/solution-space), or problem is ambiguous (/problem-space, /problem-statement).
The Execute Process
Step 1: Pre-flight Check
Before writing code, verify alignment:
More from open-horizon-labs/skills
dissent
Devil's advocate. Seek contrary evidence before locking in. Use when about to make a significant decision, when confidence is high but stakes are higher, or when the team is converging too quickly.
89review
Check work and detect drift before committing. A second opinion that catches misalignment early. Use at natural pause points, before PRs, or when something feels off.
82ship
Deliver code to users. Optimize the path from merged code to working install. Use when execution is complete and you need to get changes into users' hands.
82problem-space
Map what we're optimizing and what constraints we treat as real. Use before jumping to solutions, when hitting repeated blockers, or when patches keep accumulating.
80problem-statement
Define the framing of a problem. Change the statement, change the solution space. Use when starting work, when solutions feel wrong, or when you suspect an X-Y problem.
78solution-space
Explore candidate solutions before committing. Use when you have a problem statement and need to evaluate approaches - band-aid, optimize, reframe, or redesign.
76