sb-ship
Installation
SKILL.md
sb-ship — graduate, preserving history
Event-triggered when an Explore iteration meets the graduation gate. The one rule that matters:
preserve the experiment — cp, never git mv. The Explore story stays as design history;
git mv here is the destructive bug propagate-workflow.md exists to prevent. Load
references/propagate-workflow.md before any Ship action — it's the only reference
this skill needs; Do NOT load the sb-wrappers/sb-audit refs (lifecycle, galleries, composition) for
a Ship.
Decide the path (ask yourself)
- Did the Explore define its own component file, or iterate on an existing one? → Path A vs Path B.
- Path B: evolve in place (B1) or keep V1 in
_legacy/(B2)? B2 only when V1 still has live callsites needing a migration window. - Did the import path change? If yes →
ast-grepcallsites. If not → skip it. - Other tagged stories that should flip? (a Compare
decision:pending→decision:chosen+ winner.)