salvage
/salvage
Extract learning from work before restarting. Code is cheap; learning is the asset.
When to Use
Invoke /salvage when:
- Work is drifting - approach has changed direction multiple times
- Scope expanding while "done" keeps fuzzing - the finish line keeps moving
- Starting over feels right - but you don't want to lose what you learned
Do not use when: Work is on track and converging. Salvage is for extraction before restart, not routine reflection.
The Salvage Process
Step 1: Acknowledge the State
"This session/approach is being salvaged because [reason]. The original aim was [aim]. What happened was [reality]."
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