Stats
Actions
Tags
From claude-kanban
Use when working in a kanban-tracked project (the SessionStart briefing said 'You are working in claude-kanban project ...'). Tells you when to proactively invoke /claude-kanban slash commands to keep README, Plan, Design, Note, Tasks, and Spikes up to date without the user asking.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-kanban:using-claude-kanbanThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is your reference for *when* to invoke each `/claude-kanban:*` slash command. Invoke commands **without waiting to be asked** whenever a trigger fires. Be terse — log only what you would not want to lose. Never log obvious or trivial chatter.
This skill is your reference for when to invoke each /claude-kanban:* slash command. Invoke commands without waiting to be asked whenever a trigger fires. Be terse — log only what you would not want to lose. Never log obvious or trivial chatter.
claude-kanban has two distinct writing patterns. Pick the right one for the situation.
| Mode | When to use | Commands |
|---|---|---|
| Append | A small, dated entry. The doc keeps growing. | :note / :note plan / :note design / :spike |
| Restructure | The shape of the doc needs to change. The doc gets rewritten thoughtfully. | :readme / :plan / :design |
If you're tempted to use a restructure command for a one-paragraph update, use append instead. Restructure is heavier and meant for genuine shape changes.
/claude-kanban:note plan <one paragraph>Fire when you make a planning decision worth keeping:
Goes to Plan.md → Decision log. Reconciler-appended.
/claude-kanban:note design <one paragraph>Fire when you make a technical decision worth keeping:
Goes to Design.md → Decision log. Reconciler-appended.
/claude-kanban:note <body>Fire for everything else worth remembering that isn't a plan, design, or task:
Goes to Note.md. Direct-write append (Note.md is user-owned).
/claude-kanban:spike <slug>Fire before spending a self-contained chunk of effort on:
Creates Spikes/<date>-<slug>.md. Write findings as you go.
/claude-kanban:readme <intent>Fire when:
Do not fire for small updates — those usually go in :note instead.
/claude-kanban:plan <intent>Fire when the shape of Plan.md should change:
Preserves the Decision log section (owned by :note plan).
/claude-kanban:design <intent>Fire when the shape of Design.md should change:
Preserves the Decision log section (owned by :note design).
/claude-kanban:task (no args)Fire when multiple tasks were discussed or split out of one larger item in chat. The command will:
Tasks.md BacklogUse this when a planning conversation produces 3+ discrete work items and you want them captured without forcing the user to retype each one.
/claude-kanban:task <exact text>Fire when you (or the user) are about to start work on a specific task that already exists in Backlog. Moves it to Doing and attaches the current session.
If no matching Backlog card exists, a new Doing card is created with the given text.
/claude-kanban:task-new <text>Fire when a single new task should be created and immediately picked up. Goes straight to Doing.
Contrast with :task (no args): use :task when several tasks emerged from discussion; use :task-new when you have one task and you're starting it now.
/claude-kanban:task-doneFire when the task currently claimed by this session is complete. Moves it to Done.
/claude-kanban:task-block <reason>Fire when you can't make progress on the claimed task because of an external blocker. Records the reason and moves the card to Blocked.
These help when the right command isn't obvious:
:note plan AND :note design. Don't try to merge them.:note vs :plan/:design: Default to :note. Use the restructure commands only when the shape of the document needs to change. Daily decisions are append items.:readme, :plan, :design) always Read the file before they Write. Don't skip that step.:project <slug>.readme_updated / plan_updated / design_updated events for the audit log. You don't need to log a separate :note decision unless the change has prose worth preserving in its own right.Things to not do:
:task if you're not actually about to work on it. That's what :task-new is for if you're creating; :task is for claiming intent to start.:plan / :design to add a one-line note. That's :note plan / :note design. Restructure commands are for shape changes.:spike is for self-contained investigations with a real question. "Let me check this one file" doesn't need a spike.:readme when the user asks or when a major pivot demands it.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub trung-persefoni/claude-central-board --plugin claude-kanban