Engineering
kanban-based-development avatar

kanban-based-development

Autonomous, parallel-safe development workflow using kanban-md. Coordinates multi-agent and human efforts with atomic claims, worktrees, and explicit handoffs.

Introduction

The kanban-based-development skill provides a robust, agent-first framework for managing software development lifecycles in shared repositories. Designed specifically for multi-agent environments, it leverages the kanban-md system to prevent common conflicts such as duplicate work and race conditions. By utilizing atomic claim-and-move primitives, the skill ensures that each agent operates exclusively on a single assigned task, maintaining board integrity while facilitating seamless handoffs between automated processes and human developers. It is an essential tool for engineering teams requiring structured, autonomous task execution.

  • Coordinates collaborative development using atomic claims to prevent race conditions and duplicate effort across multiple agents.

  • Implements a standardized worktree lifecycle: pick, claim, implement, test, commit, and merge to main.

  • Features built-in 'defer-to-user' protocol, triggering human intervention for complex product decisions, credential management, or merge conflicts.

  • Supports TDD workflows by encouraging the creation of failing tests in isolated git worktrees before implementation.

  • Provides a consistent operational structure for board-based work, using file-based storage with YAML frontmatter to ensure zero-dependency, plain-text reliability.

  • Always run kanban-md commands from the canonical board home directory to ensure board-wide visibility.

  • Maintain an active status of one task per agent; strictly adhere to the 'claim before editing' rule.

  • Use the provided bash tools including git, go, golangci-lint, and kanban-md CLI to facilitate task progression.

  • Always generate a unique agent name (e.g., quiet-storm) at the session start for persistent identification in claims.

  • If a task exceeds the claim timeout, use the edit command to refresh the claim, ensuring the agent retains control until completion.

  • Use the review column as a formal handoff point for tasks requiring external decisions or environmental configuration.

Repository Stats

Stars
122
Forks
12
Open Issues
3
Language
Go
Default Branch
main
Sync Status
Idle
Last Synced
May 3, 2026, 03:11 PM
View on GitHub