using-kanban

Plan and track hierarchical Kanban work items with YAML frontmatter metadata and states.

3|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/falconnt/windsurf-skills --skill using-kanban
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-kanban
Source: https://github.com/falconnt/windsurf-skills/tree/main/using-kanban
Command: npx skills add https://github.com/falconnt/windsurf-skills --skill using-kanban

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kanban helps teams manage work items and track progress, providing a visual workflow to manage backlogs, epics, features, stories, and tasks.

Core Features & Use Cases

  • Hierarchical item structure: epics → features → stories → tasks, with frontmatter metadata for each item.
  • State tracking: ToDo, InProgress, InReview, Done, Blocked, with blocked_reason support.
  • Backlog management and sprint planning: organize work into iterations, track progress across multiple items.
  • Not for ad-hoc fixes: use /fix-errors for quick issues.

Quick Start

Start by initializing a Kanban root at .kanban/, create an epic in .kanban/epics/epic-001 and a feature under it, then add a story under the feature and a task under the story.

Frequently Asked Questions about using-kanban

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

FAQPage Schema
How do I track project backlog and sprint progress using a Kanban workflow?

Kanban workflow tracks project backlog and sprint progress by organizing work items into a hierarchical folder structure with YAML frontmatter metadata, enforcing state transitions across ToDo, InProgress, InReview, Done, and Blocked.

How does Kanban state tracking work for epics, features, and stories?

Kanban state tracking applies a strict state model across epics, features, stories, and tasks, requiring each item to hold YAML-frontmatter metadata to track ToDo, InProgress, InReview, Done, or Blocked statuses including blocked_reason support.

What is the best way to organize development tasks into epics and stories for project management?

Organize development tasks by creating a folder-based hierarchy under a Kanban root, placing epics in the epics directory, nesting features beneath them, and adding stories and tasks sequentially with frontmatter metadata.

Can I use Kanban backlog grooming for cross-team progress tracking and sprint planning?

Kanban backlog grooming supports cross-team progress tracking and sprint planning by visually managing work items across iterations, allowing teams to organize features and stories while monitoring state transitions.

When should I not use a Kanban board for managing work items?

Kanban boards should not be used for ad-hoc fixes or quick issues, as this workflow is designed specifically for structured backlog grooming, epic and feature creation, sprint planning, and cross-team progress tracking.

Why does my Kanban workflow require YAML frontmatter metadata for task tracking?

Kanban workflow requires YAML frontmatter metadata to enforce the state model and folder-based hierarchy, ensuring each epic, feature, story, and task maintains consistent tracking data for backlog management and sprint planning.