Kanban

Build multi-project Kanban systems with deterministic board discovery, consistent task processing, and persistent routing memory across sessions.

Security Scan

The skill's requirements, instructions, and claimed behavior are internally consistent: it is an instruction-only Kanban manager that reads and writes local board files and does not request external credentials or installs.

Purpose & Capability

The skill's name and description (multi-project Kanban with persistent routing memory) match the instructions: all required actions are limited to creating, reading, and updating local board/memory files under ~/kanban/ or a workspace .kanban/. No unrelated binaries, credentials, or services are requested.

Instruction Scope

SKILL.md and the auxiliary documents only instruct the agent to resolve project context, follow discovery rules, validate/repair board files, and update local index/memory/log files. The instructions do not ask the agent to read arbitrary system files, access network endpoints, or transmit data externally. They do require the agent to determine the 'current workspace root' (expected for workspace-local mode) and to read/write the specified Kanban paths.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. Nothing is downloaded or written by an installer, so there is no install-time risk.

Credentials

The skill requests no environment variables or credentials. Its file access is limited to the declared Kanban locations (~/kanban/ or {workspace}/.kanban/), which is proportionate to its purpose. The memory/index files explicitly say not to store secrets.

Persistence & Privilege

The skill is not marked always:true and does not request elevated or platform-wide persistence. It writes its own local files (memory/index/projects) which is expected behavior for maintaining Kanban state and is scoped to the declared directories.

Assessment

This skill appears to do only local Kanban bookkeeping. Before installing, confirm you are comfortable with the agent reading and writing files under ~/kanban/ (or project .kanban/ directories). Ensure the agent process that will run skills has appropriate filesystem permissions (so it can create/read/write those paths) and that you trust it not to be given broader FS/network permissions. If you need stricter control, ask the agent to keep boards workspace-local or to avoid creating memory files without explicit confirmation.

Setup

If ~/kanban/ does not exist or is empty, read setup.md silently and initialize only after user confirmation.

When to Use

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.

Architecture

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

Quick Reference

Use the smallest relevant file for the current task.

Topic	File
Setup behavior	setup.md
Memory and registry template	memory-template.md
Board schema and examples	board-template.md
Where to find each project board	discovery-protocol.md
How to process and update cards	processing-rules.md

Core Rules

1. Resolve Project Context Before Reading or Writing

• Run the discovery sequence in discovery-protocol.md at the start of each conversation.
• If project scope is ambiguous, ask once before writing.

2. Persist Routing So Any Agent Can Continue

• 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.

3. Allow Custom Board Shapes with a Stable Core Schema

• 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.

4. Process Cards Deterministically

• Follow the exact decision order in processing-rules.md for prioritization and movement.
• Never skip blockers, dependencies, or explicit WIP limits.

5. Keep Writes Atomic and Logged

• 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.

6. Keep Project Boards Isolated

• 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.

7. Preserve Continuity Across Conversations

• 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.

Common Traps

• 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.

Security & Privacy

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.

Related Skills

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

Feedback

• If useful: clawhub star kanban
• Stay updated: clawhub sync