skills.rest
jin-bo
jin-boCOMMUNITY
Explore all skills by this author →
GitHub

kanban-tasks

Break down feature requirements into atomic task cards with acceptance criteria.

94|7|Updated Feb 10, 2026
Search Tags:#task management#workflow automation#agile#kanban#sub-agent#artifact tracking#requirement breakdown
One-click install
npx skills add https://github.com/jin-bo/agentao --skill kanban-tasks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kanban-tasks
Source: https://github.com/jin-bo/agentao/tree/main/examples/skills/kanban-tasks
Command: npx skills add https://github.com/jin-bo/agentao --skill kanban-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill eliminates the chaos of scattered task tracking, manual status updates, and unverifiable requirement breakdowns for software development projects, ensuring every task is atomic, trackable, and tied to clear acceptance criteria.

Core Features & Use Cases

  • Atomic Task Breakdown: Break down feature requirements into small, independently verifiable task cards with explicit dependencies and acceptance criteria, following the Survey → Classify → Prescribe → Verify workflow.
  • Automated Status Workflows: Automate task status transitions from INBOX to DONE, with support for both offline mock execution for CI safety and real sub-agent execution for automated task processing.
  • Local Task Dashboard: Run a background daemon and web UI to visualize task progress, track artifacts, and monitor execution in real time, all hosted locally for privacy. Use Case: For a development team building a new user authentication feature, use this Skill to break the feature into testable tasks (e.g., split the auth module into pure functions, write unit tests for the login flow), track progress across the team, and run automated checks to verify each task meets acceptance criteria.

Quick Start

Use the kanban-tasks skill to initialize a kanban board for your current project, break down your top priority feature into atomic task cards with clear acceptance criteria, and start tracking progress via the local web UI.

Frequently Asked Questions about kanban-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down feature requirements into verifiable task cards for agile development?▼

To break down feature requirements into verifiable task cards, you follow a workflow of Survey, Classify, Prescribe, and Verify. This process ensures every task is atomic, independently trackable, and tied to clear acceptance criteria for software development projects.

Can I run a local kanban board to track software development task progress?▼

Yes, you can run a local daemon and web UI service to visualize task progress and monitor execution in real time. This local task dashboard is hosted privately on your machine to track artifacts and manage workflow status transitions.

Does kanban board task automation support CI safety with mock offline execution?▼

Kanban board task automation supports CI safety through mock offline execution. This allows automated status transitions from INBOX to DONE to be simulated without affecting real environments, alongside a real sub-agent execution mode for actual automated task processing.

What is the best way to automate task status transitions for workflow automation?▼

The best way to automate task status transitions for workflow automation is by using a structured kanban workflow that includes built-in guardrails for lock management, artifact retention, and dependency tracking. This eliminates manual status updates and ensures tasks move correctly from INBOX to DONE.

Do I need pyyaml installed to manage tasks with kanban boards?▼

Yes, you need the pyyaml dependency installed to manage tasks with kanban boards using this specific skill. This library is required to parse the configuration files that define the structured kanban workflow and task properties.

Are there limitations when using sub-agent execution for automated task processing?▼

When using sub-agent execution for automated task processing, you must account for built-in guardrails managing lock states, artifact retention, and dependency tracking. While it automates status transitions, incorrect dependency mapping can block the automated workflow from progressing to DONE.

Related Skills

Explore More Software Engineering Skills→
MakisuoMakisuo
1.6k

clickhousectl-local-dev

Install and configure a local ClickHouse environment with clickhousectl.

Community
Intermediate
ramontramontiniramontramontini

pull

Execute downstream stories from ready_to_pull to done with enforced gates.

Community
Advanced
PhucMPhamPhucMPham

plans-kanban

Serve a Kanban dashboard for plan.md-based plans with progress and timelines.

Community
Advanced
alanxuroxalanxurox
36

mission-control

Coordinate team tasks, messaging, and status updates via CLI.

Community
Intermediate