Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From ship
Breaks a plan, spec, or PRD into independently-grabbable vertical-slice issues and publishes them to GitHub in dependency order.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ship:slice [plan / spec / PRD / issue ref]When to use
break plan into issues, plan to issues, spec to issues, vertical slice, tracer bullet, split into issues, slice
[plan / spec / PRD / issue ref]opusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Break a plan into independently-grabbable issues. Each issue is a tracer bullet, a thin slice cutting end-to-end through every layer (schema / API / UI / test), demoable or verifiable on its own.
Break a plan into independently-grabbable issues. Each issue is a tracer bullet, a thin slice cutting end-to-end through every layer (schema / API / UI / test), demoable or verifiable on its own.
Take the plan source from $ARGUMENTS. For an issue reference (number / URL / path), fetch the body and comments via gh issue view <N>. If empty, work from a plan already in conversation context; if none, ask what to break down via AskUserQuestion.
| Skill | Output | Medium / timing |
|---|---|---|
| /slice (this) | Durable GitHub issues in dependency order | A queue for a human to pick up later |
| /issue | One issue (premise + critic verification) | File a single request |
| architect-feature + /swarm | Ephemeral in-session parallel blueprint | Design for implementing now |
/slice's value is decomposition and dependency-ordered publish. For one issue use /issue. To implement now use /swarm.
Work from the plan in conversation context. If $ARGUMENTS carries an issue reference, read its body and comments.
If not yet explored, understand the current state. Issue titles / descriptions follow the project glossary and respect ADRs in the area you touch. Look for prefactor opportunities that make the change easier ("make the change easy, then make the easy change"). Spawn one Explore agent only when a cross-cutting sweep is needed; no per-slice spawns.
Split the plan into tracer-bullet issues. Vertical slices (through all layers), not horizontal (one layer only).
| Rule | Content |
|---|---|
| All layers | Each slice cuts through every layer (schema / API / UI / test) |
| Self-verifiable | A completed slice is demoable or verifiable on its own |
| Prefactor first | If prefactoring is needed, put it in the first slice |
Present the proposed breakdown as a numbered list. For each slice show the following.
| Field | Content |
|---|---|
| Title | Short descriptive name |
| Blocked by | Which other slices must complete first (if any) |
| User stories | Which user stories this slice covers (if any) |
Ask: does the granularity feel right (too coarse / too fine), are the dependencies correct, should any slices be merged or split. Iterate until the user approves.
After approval, confirm once more via AskUserQuestion before batch publish ("Create these N issues?"). Creating N issues is outward-facing and hard to unwind, so never auto-publish without confirmation.
On approval, publish in dependency order (blockers first). Create blockers first and capture their numbers so "Blocked by" can reference real issue numbers. Use the template below and Sandbox-Compatible Create per issue. Do not attach a triage label (AFK consumer wiring is out of scope). Do not close or modify any parent issue.
## Parent
A reference to the parent issue (only if the source was an existing issue; otherwise omit this section).
## What to build
A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation. Avoid specific file paths or code snippets, which go stale fast. Exception: a snippet a prototype produced that encodes a decision more precisely than prose (state machine / reducer / schema / type). Note it came from a prototype and trim to the decision-rich parts.
## Acceptance criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
## Blocked by
- A reference to the blocking ticket (if any)
Or "None - can start immediately" if no blockers.
Read language from ${CLAUDE_SKILL_DIR}/../../settings.json and translate the issue body into that language. Default to English if unset. Keep technical terms / code / identifiers untranslated.
cat > /tmp/claude/slice-body.md << 'EOF'
<body>
EOF
gh issue create --title "<title>" --body-file /tmp/claude/slice-body.md
mv /tmp/claude/slice-body.md ~/.Trash/ 2>/dev/null || true
Repeat this in dependency order for multiple slices, capturing each issue number from the publish output to fill into later "Blocked by" fields.
| Error | Action |
|---|---|
| No plan source | Ask what to break down via AskUserQuestion |
| Issue ref unresolvable | Report the ref and stop |
| No git repository | Report "Not a git repo" |
| gh auth failure | Report the auth error |
| Publish fails midway | Report created numbers and ask whether to resume |
## Slice breakdown (N)
1. <Title>
- Blocked by: <slices or none>
- User stories: <ids or none>
List published issues in dependency order.
Created (dependency order):
- #<number> <title> (blocked by: #<n> | none)
npx claudepluginhub thkt/dotclaude --plugin shipBreaks a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Guides through drafting, quizzing, and publishing issues.
Breaks plans, specs, or PRDs into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Useful for turning high-level direction into actionable, demoable tasks.
Breaks plans, specs, or PRDs into independently-grabbable issues using tracer-bullet vertical slices. Useful when converting a plan into implementation tickets.