From kanban
Break work into stories and subtasks on the Kanban board. Use when the user describes a feature, task, or body of work that should be planned, decomposed, or organized into trackable tickets.
npx claudepluginhub gablabelle/claude-plugins --plugin kanbanThis skill is limited to using the following tools:
You are planning work by breaking it into stories and subtasks on the mcp-kanban board.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
You are planning work by breaking it into stories and subtasks on the mcp-kanban board.
You MUST call mcp__kanban__open_board FIRST, before any other kanban tool. This starts the web UI server. Wait for it to return, then open the URL in the browser:
open "<url from open_board>"
Do NOT call list_columns, list_tickets, create_ticket, or any other kanban tool until this step is complete.
Use mcp__kanban__list_columns to get the available columns and their IDs. Identify which column is best for new planned work (typically "Backlog" or "Todo").
Use mcp__kanban__list_tickets to check for existing tickets so you don't create duplicates.
Read relevant code files to understand the current state. Break the work described in $ARGUMENTS into:
For each story:
mcp__kanban__create_ticket — use a clear title and a description that explains the goal, acceptance criteria, and any relevant technical contextmcp__kanban__create_subtask — each subtask should have a concise title and a description covering what specifically needs to be donePlace stories in the "Backlog" or "Todo" column (whichever makes more sense given the board's column structure).
Set appropriate priorities: urgent for blockers, high for critical path items, medium for standard work, low for nice-to-haves.
After all tickets are created, present a summary:
Then ask the user: "The plan is on the board. Would you like me to start working through these tickets?"
If the user confirms, invoke the kanban-work workflow.