solution-space
/solution-space
Explore candidate solutions before committing. The trap is defending the first workable idea.
Sits between Problem Statement and Implementation. You have the problem framed; now map approaches before picking one.
When to Use
- Problem is understood — you have a clear problem statement
- Multiple approaches viable — not obvious which path is best
- About to start coding — pause and explore first
- Patches accumulating — third config flag for the same bug
- Attached to first idea — that's the warning sign
Skip when: Still clarifying the problem. Use /problem-statement first.
The Local Maximum Trap
Exploration is cheap. The failure mode is defending the first solution that works.
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.
80execute
Do the work. Pre-flight, build, detect drift, salvage if needed. Use when you have a clear aim and are ready to implement.
79problem-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.
78