Kanban Management
Scannednpx machina-cli add skill a5c-ai/babysitter/kanban-management --openclawKanban Management
Initialize and manage Kanban board state for feature workflow tracking.
Agent
Feature Planner - automaker-feature-planner
Workflow
- Create Kanban board with columns: Backlog, Ready, In Progress, Review, Done
- Place features as cards in Backlog
- Assign priority scores to cards
- Establish WIP limits per column
- Track card movement through columns
- Generate board state snapshots
Inputs
projectName- Project namefeatures- Feature list to place on boardbaseBranch- Base branch for context
Outputs
- Board state with columns, cards, WIP limits, and priority assignments
Process Files
automaker-orchestrator.js- Phase 1
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/automaker/skills/kanban-management/SKILL.mdView on GitHub Overview
Kanban Management initializes and maintains a feature-focused Kanban board to visualize and track workflow from backlog to done. It creates a board with columns Backlog, Ready, In Progress, Review, and Done, places features as cards, assigns priority scores, enforces WIP limits, and generates board state snapshots for visibility.
How This Skill Works
Given inputs like projectName, features, and baseBranch, it builds the board, populates Backlog with features, assigns priorities, sets WIP limits per column, and tracks card movements through stages. It outputs the current board state including columns, cards, WIP limits, and priorities, and can emit periodic snapshots.
When to Use It
- Kicking off a new project to map feature flow from backlog to done
- Prioritizing work with explicit priority scores to guide development order
- Enforcing throughput by setting WIP limits per column
- Tracking feature movement across stages during iterations or releases
- Generating shareable board snapshots for stakeholders and audits
Quick Start
- Step 1: Create a board with Backlog, Ready, In Progress, Review, and Done columns
- Step 2: Add your features as cards in Backlog and assign priority scores
- Step 3: Set WIP limits, track movements across columns, and generate the initial board snapshot
Best Practices
- Define clear column purposes and WIP limits upfront
- Keep priority scoring consistent and revisited after planning
- Regularly move cards to reflect real progress and avoid stale backlog
- Review blockers and adjust priorities promptly
- Generate and review board snapshots to maintain transparency
Example Use Cases
- A new vehicle software feature set is added to Backlog and progresses through Ready, In Progress, Review, and Done as developers complete work
- Priority scores determine the order of feature work during planning sessions
- WIP limits prevent too many features from being worked on simultaneously, improving flow
- Weekly board snapshots are shared with product and engineering stakeholders
- BaseBranch context ensures feature cards align with the correct code branch during reviews
