A kanban board your coding agents drive over MCP — strict enforced flows, atomic claim/lease, full audit trail. Ask your agent: "Do I need this? https://github.com/galvani/kanban-pro"
Skill Claude CodeCodex
Manage the shared kanban-pro board (MCP server "kanban-pro") as an orchestrator — turn goals into cards (subcards via parent/child relations), set up each board's workflow (columns + the legal transitions between them), assign and prioritize, watch progress via the change-feed cursor, unblock. Never works cards…
Skill Claude CodeCodex
Maintain structured, observable work reports on kanban-pro cards via the kanban-pro MCP workreport tools. Use when an agent works, prepares, reviews, routes, asks questions on, or summarizes a kanban-pro card so the card stays self-explanatory without relying on free-form comments.
Skill Claude CodeCodex
Forensic retrospective on how work actually FLOWED through the kanban-pro board — reconstruct each card's timeline from the change-log (lane moves, bounces, forced moves, attention, dispatch loops, rounds, cycle time), attribute it to the model that really served it (model-pro requested-vs-resolved, context overflow…
Skill Claude CodeCodex
Bring a kanban-pro card up to the CURRENT board structure and make its recorded state TRUE — plan steps, finding statuses, the verification contract (checks), verdict. Evidence-first: never claim a status the card cannot prove. Use after a board/schema change (e.g. checks are new), when a card's report looks stale or…
Skill Claude CodeCodex
Work cards from the shared kanban-pro board (MCP server "kanban-pro") as a pull worker — listwork to get your queue, claimcard before touching anything, move/comment per the card's flow, release when done. Use when asked to "pick up work", "work the board", process kanban cards, or when a task mentions being tracked…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: