Menu
Manage kanban cards via CLI with commands for search, create, update, move, problem tracking, cross-agent notes, and scheduled automations
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build and maintain the Codebase Atlas for Code Mode: propose areas, write schema-validated explanation nodes via sly-atlas, declare collections for bulk file families, run staleness-driven refreshes PLUS a coverage crawl that enriches the thinnest area every run, generate the catch-up digest, author guided tours, annotate database schemas, serve atlas context to agents, and drive the Code Mode view with navigate/highlight/deck directives
Dynamic context provider for codebase knowledge. This skill should be used when working on code, answering questions about architecture, or making changes that require understanding of project structure. Maintains area-specific reference files that are loaded on demand. Self-updating based on observed drift between references and actual code. Load this skill early in work sessions - it contains essential workflow and update protocols.
Manage kanban cards via CLI with commands for search, create, update, move, reorder, problem tracking, cross-agent notes, scheduled automations, cross-card prompt execution, AI-set status line (manual + tiered auto-status), and structured questionnaires
Send responses back to the user via their messaging channel (Telegram, Slack, Teams, etc). Use this skill when a message arrives with a channel header like [Telegram], [Slack], etc.
Create a git checkpoint of ALL recent changes
Dynamic context provider for codebase knowledge. This skill should be used when working on code, answering questions about architecture, or making changes that require understanding of project structure. Maintains area-specific reference files that are loaded on demand. Self-updating based on observed drift between references and actual code. Load this skill early in work sessions - it contains essential workflow and update protocols.
| name | kanban |
| version | 1.2.1 |
| updated | "2026-02-22T00:00:00.000Z" |
| description | Manage kanban cards via CLI with commands for search, create, update, move, problem tracking, cross-agent notes, and scheduled automations |
Manage kanban cards via CLI: node scripts/kanban.js <command>
| Command | Description |
|---|---|
search | Find cards by query, stage, type, area |
show | Display full card details (NOT view) |
create | Create a new card |
update | Modify card fields |
move | Move card between stages |
archive | Soft delete a card |
checklist | Manage checklist items |
problem | Track issues on cards |
notes | Manage cross-agent notes |
automation | Configure and manage scheduled automations |
areas | List available areas |
# Always start with --help if unsure
node scripts/kanban.js --help
node scripts/kanban.js <command> --help
# Search cards
node scripts/kanban.js search "query"
node scripts/kanban.js search --stage backlog
node scripts/kanban.js search --type feature
# Show card details (use 'show', NOT 'view')
node scripts/kanban.js show card-123
# Create card
node scripts/kanban.js create --title "Add feature X" --type feature --priority medium
# Update card
node scripts/kanban.js update card-123 --title "New title" --areas "web-frontend,terminal-bridge"
# Link documentation to card
node scripts/kanban.js update card-123 --design-ref "documentation/designs/foo.md"
node scripts/kanban.js update card-123 --feature-ref "documentation/features/bar.md"
# Move card
node scripts/kanban.js move card-123 design
# Archive card
node scripts/kanban.js archive card-123
# Checklist management
node scripts/kanban.js checklist card-123 list
node scripts/kanban.js checklist card-123 add "Write tests"
node scripts/kanban.js checklist card-123 toggle check-123
# Problem tracking
node scripts/kanban.js problem card-123 list
node scripts/kanban.js problem card-123 add "Bug description" --severity major
node scripts/kanban.js problem card-123 resolve prob-123
node scripts/kanban.js problem card-123 promote prob-123 --type chore
# Agent notes
node scripts/kanban.js notes card-123 list
node scripts/kanban.js notes card-123 add "Context for next agent" --agent "Claude"
node scripts/kanban.js notes card-123 search "blocker"
node scripts/kanban.js notes card-123 edit 2 "Updated note text"
node scripts/kanban.js notes card-123 delete 3
node scripts/kanban.js notes card-123 clear
# List available areas
node scripts/kanban.js areas
show first: Before any action, run show <card-id> to see current state including existing problemsproblem <card-id> add "description"Agent notes are a shared scratchpad on each card for passing context between agents and sessions.
When to use notes:
notes <card-id> list — read what previous agents leftAlways identify yourself with --agent:
--agent "Claude"--agent "Codex"--agent "Gemini"UserLimits: Max 30 notes per card, max 3000 characters per note.
# Read notes before starting
node scripts/kanban.js notes card-123 list
# Leave context after your session
node scripts/kanban.js notes card-123 add "Completed API routes, tests passing. Frontend still needs the Notes tab wired up." --agent "Claude"
# Flag a blocker
node scripts/kanban.js notes card-123 add "Build fails on node 18 — needs --experimental flag for crypto" --agent "Codex"
When using the Onboard action on a backlog card:
node scripts/kanban.js update <card-id> \
--title "Refined title" \
--description "Structured description" \
--areas "area1,area2" \
--priority high
Cards support dedicated reference fields for documentation:
| Field | Flag | Purpose |
|---|---|---|
| Design Doc | --design-ref | Link to design document |
| Feature Spec | --feature-ref | Link to feature specification |
| Test Doc | --test-ref | Link to test documentation |
# Link design doc when moving to design stage
node scripts/kanban.js update card-123 --design-ref "documentation/designs/my-feature.md"
# Link feature spec when feature is fully specified
node scripts/kanban.js update card-123 --feature-ref "documentation/features/001_my_feature.md"
# Link test doc when test plan exists
node scripts/kanban.js update card-123 --test-ref "documentation/tests/my-feature-tests.md"
These appear as dedicated fields on the card (not in description).
# 1. View current state
node scripts/kanban.js show card-123
# 2. Update with refined details
node scripts/kanban.js update card-123 \
--title "Implement user authentication with OAuth" \
--description "Add Google and GitHub OAuth providers..." \
--areas "backend,auth" \
--priority high
# 3. Move to design when ready
node scripts/kanban.js move card-123 design
# User says: "I need to fix the login button being too small"
node scripts/kanban.js create \
--title "Fix login button size" \
--type bug \
--priority medium \
--areas "web-frontend"
# Add checklist items
node scripts/kanban.js checklist card-123 add "Unit tests pass"
node scripts/kanban.js checklist card-123 add "Integration tests pass"
node scripts/kanban.js checklist card-123 add "Manual testing complete"
# Mark as done
node scripts/kanban.js checklist card-123 toggle check-xxx
# If issues found
node scripts/kanban.js problem card-123 add "Login fails after timeout" --severity major
When a problem is too big for a quick fix and needs its own design/implementation cycle:
# Review problems
node scripts/kanban.js problem card-123 list
# Promote a problem to a new backlog card
node scripts/kanban.js problem card-123 promote prob-xxx --type chore
# The original problem is marked resolved, new card created in backlog
# Card inherits areas from source card, references original in description
Cards can be toggled into automation mode — a scheduled task that fires a prompt into a terminal session at a specified time. One card = one automation.
# Create an automation card directly
node scripts/kanban.js create --title "Nightly test run" --type chore --automation
# Toggle existing card to automation mode
node scripts/kanban.js update card-123 --automation true
node scripts/kanban.js update card-123 --automation false
# Configure automation (partial updates — only specified fields change)
node scripts/kanban.js automation card-123 configure --schedule "0 6 * * *" --prompt "Run all tests" --provider claude
node scripts/kanban.js automation card-123 configure --schedule "0 9 * * 1" # just the schedule
node scripts/kanban.js automation card-123 configure --prompt "New prompt" # just the prompt
node scripts/kanban.js automation card-123 configure --fresh-session true
node scripts/kanban.js automation card-123 configure --report-messaging true
# Enable / disable
node scripts/kanban.js automation card-123 enable
node scripts/kanban.js automation card-123 disable
# Manual trigger (calls bridge API directly)
node scripts/kanban.js automation card-123 run
# View automation status
node scripts/kanban.js automation card-123 status
# List all automation cards
node scripts/kanban.js automation list
node scripts/kanban.js automation list --tag "deploy"
Key concepts:
The CLI provides clear error messages:
Card 'xxx' not found - Check the card IDInvalid stage - Use: backlog, design, implementation, testing, doneInvalid type - Use: feature, chore, bugInvalid priority - Use: low, medium, high, criticaldocumentation/kanban.json directly--include-archived to see them)