What problem does it solve? Teams upgrading to the V6 Kanban workflow often have a flat tasks/ directory full of markdown files with no state organization. Manually sorting dozens of task files into backlog, in-progress, qa, completed, and archive folders is tedious and error-prone, and naive moves lose git history. ## Core Features & Use Cases - Automated Directory Setup: Creates the five Kanban subdirectories (backlog, in-progress, qa, completed, archive) if they do not exist. - Status-Based Classification: Reads each task file's frontmatter or body for Status: open or Status: closed markers and routes files to the correct folder, defaulting unknown files to backlog. - History-Preserving Moves: Uses git mv so all task file history is retained through the migration. - Use Case: After adopting the V6 orchestration workflow, run this once to reorganize an existing repository's 40 flat task files into the Kanban structure, then update AGENTS.md references. ## Quick Start Ask the agent to migrate the flat tasks directory into the V6 Kanban folder structure using the migrate-kanban skill.
