migrate-board

What problem does it solve? Teams tracking work in markdown files (board-context.md and docs/board/) eventually hit scaling limits: no search, no notifications, no PR integration. This Skill moves the entire board to GitHub Issues with an optional Projects v2 board, without losing history or creating duplicates. ## Core Features & Use Cases - Safe, resumable migration: Every issue creation is preceded by an exact title-prefix lookup, so an interrupted run is resumed by simply re-running the Skill — never by manual cleanup. - Board repair before migration: The bundled parser validates table structure, detects merge corruption (split tables, wrong headers, duplicate Task IDs), and reports each problem with a concrete fix before anything is written. - Tech-debt import: Optionally migrates the tech-debt backlog, merging items onto existing board tasks with severity labels or creating standalone labeled issues. - History preservation: Nothing is deleted — markdown files are frozen with a banner, and Done rows can either become closed issues or stay as frozen markdown history. - Use Case: A team whose board-context.md has grown to hundreds of tasks says "migrate board to GitHub Issues"; the Skill dry-runs the parse, creates labels and issues, links epic sub-issues, verifies both directions, then flips board_backend to github. ## Quick Start Ask the AI to migrate the markdown board to GitHub Issues by saying "migrate board" from the root of a repo that has board-context.md and a GitHub remote.