kanban
Skill4 starsChanged 19 days agoMITView on GitHub
Work the project's kanban board kept in the brain: create, work, manage, move, complete, stash and review tasks. Trigger when the user says "/kanban", "add a task", "create a task", "what should I work on", "move that task", "show the board", "stash context", "review the task", or otherwise asks to track, pick up, move or finish a piece of project work on the board.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- Jasenpan1987/multi-codetheir own version, first seen Nov 8, 2026
- lalulali/vespyrtheir own version, first seen Nov 6, 2026
- yuriih380/kanbantheir own version, first seen Oct 20, 2026
- ai4kanban/ai4kanbantheir own version, first seen Oct 17, 2026
- build-dezineer/skills-nuxt4-tw-webapptheir own version, first seen Oct 13, 2026
- lamaohub/local-kanbantheir own version, first seen Oct 11, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- cyanluna-git/cyanluna.skills★ 183same name
- ai4kanban/ai4kanban★ 52same name
- Starchild-ai-agent/official-skills★ 32same name
- lalulali/vespyr★ 11same name
- mkSteady/mkSkills★ 9same name
- flpbalada/fb-skills★ 8same name
- Adam-Dangerfield/Agent-Kanban★ 4same name
- keefar/ticket-flow★ 4same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- lamaohub/local-kanban★ 2same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- aide-brain-authorSkill
- aide-handoffSkill
- aideSkill
- brainSkill
- study-playbookSkill
The file
Files
/kanban — Kanban Board
The tasks live in the brain, one folder per project with a subfolder per column — the folders are the board. The kanban-maintainer agent does every read and write of the tasks: it reads the kanban rules and the operation guides from the brain itself and reports back compactly. You talk to the user and decide; it finds and changes. If the agent isn't available, say so and stop — never edit the board another way.
Arguments name the operation and its input, e.g. /kanban create "...". If no operation is given, ask the user which one.
- Project tag. Every request to the agent carries the project's tag. Look for it first in the project's instructions file (
CLAUDE.md,AGENTS.mdor your framework's equivalent), on a line readingKanban project tag: <tag>. If there is no such line, ask the user which project the work is for, then add that line to the instructions file yourself and tell the user you recorded it, so no later session asks again. Never guess the tag. - Finding tasks. Never list or search the project's tasks yourself. Ask the agent to LIST or FIND tasks: it reports each task's column, slug, priority, title, a short excerpt and its path. A single task is small — read it in full from that path whenever you need more than the excerpt.
- Approve, then apply. Before any change except a stash, show the user exactly what will change — which task moves from which column to which, or the new task's title, priority, type, description and column — and get a clear yes. Ask for anything missing first: a create needs a title and a priority (
p0critical,p1high,p2low,p3lowest); a move needs a column (Backlog, Todo, In Progress, In Review, Done). Then send the agent an APPLY naming each change by slug, and tell the user what it reports. - create, move, complete — approve, then APPLY. Move and complete act on the task this session is working on; name it by slug, and ask if it isn't clear. Complete goes to In Review, or to Done when the user asks.
- manage — have the agent LIST the open tasks and CHECK the cleanup rules, show both to the user, ask what to move and which cleanup items to apply, approve, then APPLY.
- stash — write the content yourself from the conversation, since only you have it: changes made, decisions and why, open questions, remaining work, gotchas. APPLY it into the session's task without asking first — a stash only appends a record of the session and moves or creates nothing. The agent formats and appends it; tell the user it was stashed.
- work and review — these plan, implement, test and fix, not just board work. Read the kanban index
kanban/kanban.mdfrom the brain, then only the guide it links for the operation, and follow it step by step. Every board or task change inside it still goes to the agent, approved as above (stashes excepted).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

