Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build multi-project Kanban systems with deterministic board discovery, consistent task processing, and persistent routing memory across sessions.
Build multi-project Kanban systems with deterministic board discovery, consistent task processing, and persistent routing memory across sessions.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
If ~/kanban/ does not exist or is empty, read setup.md silently and initialize only after user confirmation.
Use this skill when the user wants a Kanban system the agent can maintain across projects and conversations. The agent should build project-specific boards, remember where each board lives, and process tasks with consistent rules.
Memory lives in ~/kanban/. See memory-template.md for base files, board-template.md for board structure, and discovery-protocol.md for project routing. ~/kanban/ βββ memory.md # Global status, integration, defaults βββ index.md # Project registry and board location map βββ templates/ β βββ board-template.md # Canonical board format copy βββ projects/ βββ {project-id}/ βββ board.md # Active board for this project βββ rules.md # Project-specific lane and policy definitions βββ log.md # Board write log βββ archive/ Optional project-local mode: {workspace}/.kanban/ βββ board.md βββ rules.md βββ log.md
Use the smallest relevant file for the current task. TopicFileSetup behaviorsetup.mdMemory and registry templatememory-template.mdBoard schema and examplesboard-template.mdWhere to find each project boarddiscovery-protocol.mdHow to process and update cardsprocessing-rules.md
Run the discovery sequence in discovery-protocol.md at the start of each conversation. If project scope is ambiguous, ask once before writing.
Keep the Kanban index file updated with workspace path, project aliases, and primary board path. After each successful write, update last_used for the project entry.
Users can rename lanes or add custom columns per project in the project rules file. Every card must keep parseable core fields: id, title, state, priority, owner, updated.
Follow the exact decision order in processing-rules.md for prioritization and movement. Never skip blockers, dependencies, or explicit WIP limits.
Update the board file and append one line to the project log in the same operation cycle. If a write fails midway, report partial state instead of claiming success.
Never move or edit cards across different project boards without explicit user intent. For cross-project requests, produce a plan first, then apply updates per board.
On first message of a new conversation, resolve board location and load current state before proposing work. If no board exists, initialize from board-template.md, register it in the index file, and continue.
Using one global board for all projects -> priorities and ownership become ambiguous. Renaming lanes without updating state mapping in the project rules file -> cards become unprocessable. Writing board updates without refreshing the index file -> next agent session cannot locate the board. Keeping tasks without IDs -> duplicate card updates and broken references. Marking work as done without log entry -> no audit trail for later sessions.
Data that stays local: Board files and project registry in ~/kanban/ or {workspace}/.kanban/. Data that leaves your machine: None by default. This skill does NOT: Make undeclared network requests. Modify files outside the selected Kanban scope. Invent board history when logs are missing.
Install with clawhub install <slug> if user confirms: workflow - operational workflow design and execution loops projects - project organization and cross-project governance delegate - owner assignment and task handoff protocols daily-planner - daily planning and task sequencing
If useful: clawhub star kanban Stay updated: clawhub sync
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.