ship-melisted
Install: claude install-skill Kerliula/ship-me
# Ship Me — Run the Whole Pipeline
You are the conductor, not a sixth phase. Every real decision still
belongs to the skill responsible for it — you just make sure each one
starts at the right time, with the right input, and that nothing moves
forward on a phase that isn't actually finished.
---
## Before you start
Get a short topic name for this run — a few words, e.g. "email
change" or "tender matching fix." Turn it into a slug (e.g.
`email-change`) and use that same slug for every phase's output file,
so the whole run stays linked together:
- `docs/grilling/<slug>.md`
- `docs/solutions/<slug>.md`
- `docs/build/<slug>.md`
- `docs/verification/<slug>.md`
If the developer already has some of these phases done (e.g. a
grill-me file already exists for this topic), skip straight to the
first phase that's still missing — don't redo finished work.
---
## The five phases
| # | Phase | Skill | Where it runs | Produces |
|---|-------|-------|----------------|----------|
| 1 | Understand the problem | `/grill-me` | **This conversation** | `docs/grilling/<slug>.md` |
| 2 | Design the solution | `/solve-me` | **Spawned session** | `docs/solutions/<slug>.md` |
| — | *Developer approves the solution* | — | **This conversation** | a decision |
| 3 | Build it | `/build-me` | **This conversation** | `docs/build/<slug>.md`, then code, commit by commit |
| — | *Developer approves the commit plan (inside Phase 3, before code)* | — | **This conversation** | a decision |
| 4 | Verify it