# Ship Kanban > PoketoWork kanban variant of ship — package finished work and update the matching card - Skill: `georgeqle/ship-kanban` (Agent Skill) - Install (CLI): `npx skillmds@latest add georgeqle/ship-kanban` - Raw SKILL.md: https://api.skillmd.com/api/skills/georgeqle/ship-kanban/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: GeorgeQLe (https://skillmd.com/u/georgeqle) - Updated: 2026-09-09 - Page: https://skillmd.com/skills/georgeqle/ship-kanban --- # Ship Kanban Invoke as `$ship-kanban`. Use this skill only in projects that have opted into a PoketoWork kanban pack. ## Process 1. Follow the base `$ship` workflow exactly, passing through `$ARGUMENTS`. 2. Resolve and validate the project board using `tasks/.kanban-board`, `poketo kanban boards`, and the standard lists: Backlog, Todo, In Progress, Done, Punt. 3. After shipping: - Find the completed step card. - If the step is checked off, move it to Done and mark it done. - If the step is blocked or deferred, move it to Punt and add the reason. - If status is unclear, ask the user. - Update the card description with commit SHAs. 4. After planning, ensure the next step card exists in Todo: move from Backlog, create if missing, or skip if already Todo or later. 5. Suggest the top Todo card by priority: overdue, starred, then list order. If no Todo cards exist, check Backlog. Kanban failures are advisory and must not block the base ship workflow. ## Next-Step Routing In the final response, include either `Recommended next skill: ` or the two-line pair `**Next work:** ` and `**Recommended next command:** `. Route to the matching kanban workflow when board state can advance; otherwise route to the documented non-kanban fallback or say `No follow-up skill recommended` with the reason. ## Default Shipping Contract Follow the shared shipping contract convention in CLAUDE.md.