agent-migrate

Migrates markdown workflow files into a GitHub Project board with backup and mapping report.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill agent-migrate-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-migrate
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/agent-migrate
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill agent-migrate-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams tracking work in local markdown files (BACKLOG.md, TODO.md, DONE.md, plans/, tasks/) lack the visibility and collaboration features of a real project board, and manually recreating that state in GitHub Projects is error-prone and tedious. ## Core Features & Use Cases - One-shot migration: Parses backlog, todo, done, plan, and task markdown files and pushes them to a GitHub Project board as issues, plan comments, and sub-issues with correct statuses and labels. - Idempotent and auditable: Detects already-migrated items via markers, creates a timestamped backup with SHA-256 manifest, and writes a full MAPPING.md report linking every source line to its destination issue. - Interactive ambiguity resolution: Prompts the user to match unmatched plans and tasks, choose done-item import policy, and confirm archiving of source markdown. - Use Case: A project using a markdown-based agent workflow wants to switch to the github_project backend; running /agent-migrate provisions the board, migrates all items, updates agent.yaml, and stages the archive for review. ## Quick Start Run /agent-migrate from the project root to migrate the existing .workflow markdown files into a GitHub Project board.

Frequently Asked Questions about agent-migrate

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

FAQPage Schema
How do I migrate markdown backlog files to a GitHub Project board?▼

Run /agent-migrate from the project root after configuring agent.yaml. The skill parses BACKLOG.md, TODO.md, DONE.md, plans/, and tasks/, then creates issues, plan comments, and sub-issues on the board via the board-man agent.

Is the markdown to GitHub Projects migration safe to re-run?▼

Yes, the migration is idempotent. Already-migrated items are detected through find-issue-by-marker lookups and skipped, so re-running after a partial failure continues where it stopped without creating duplicates.

What GitHub permissions are required for the migration?▼

The gh CLI token must include the project scope, verified via gh auth status. If missing, run gh auth refresh -s project before starting, otherwise the skill stops at the pre-flight check.

Does the migration delete my original markdown files?▼

No. Source files are first copied into a timestamped backup with a SHA-256 manifest. Archiving via git mv happens only in the final step after explicit user confirmation, and nothing is committed automatically.

What happens to tasks from a different repository during migration?▼

Tasks whose Repo metadata does not match the configured single-repo board still get created as sub-issues, but a warning is printed and recorded in the mapping report since coders may not match them. Multi-repo support is a follow-up.