migrate — Claude Code and Codex command: Task Master to markdown
migrate — a slash command that takes a project off Task Master MCP and onto task files in markdown, carrying open tasks over before clearing the old setup.
Elastic-2.0 ★ 155 updated 2026-10-29
/plugin marketplace add serpro69/claude-toolbox
/plugin install kk@claude-toolboxWhat migrate does
The command moves a project off Task Master MCP and onto task files in markdown. First a check for leftovers: .taskmaster/, .claude/commands/tm/, the task-orchestrator, task-executor and task-checker agents, task-master-ai entries in .claude/settings.json, Task Master headings in CLAUDE.md. Find none of those and it says there is nothing to migrate, then stops.
Open tasks arrive through the mcp__task-master-ai__get_tasks tool, asked for pending items with subtasks; with no MCP server attached it falls back to .taskmaster/tasks/tasks.json. Statuses get remapped: deferred turns into blocked with the reason kept, review becomes in-progress, done and cancelled are dropped. Each feature lands in /docs/feat/wip/[feature]/tasks.md, shaped after ../../skills/design/example-tasks.md, and you see the list before anything is deleted.
Cleanup takes the .taskmaster/ tree, .claude/commands/tm/, the task agent files, Task Master sections in CLAUDE.md and the allow/deny entries in .claude/settings.json; the template-sync script is refetched with curl. Your ~/.claude.json stays untouched, so pulling the task-master-ai entry out of mcpServers is on you. A closing summary suggests /clear once the permission config changed.
What it helps with
- port open Task Master tasks into markdown files
- strip
.taskmaster/and thetm/slash commands from a repo - drop
task-master-aipermissions from.claude/settings.json - clear Task Master sections out of
CLAUDE.md - refresh the template-sync script after the switch
Example prompts for the agent
- Run
/migrateand list the open Task Master tasks before writing anything /migrateon this repo, and stop early if there is no.taskmaster/here- Go through
/migratebut show me every file you plan to delete first
How to install migrate
1Plugin marketplace
/plugin marketplace add serpro69/claude-toolbox/plugin install kk@claude-toolbox2Manually: put the files in place
.claude/commands/migrate.mdCall it with /migrate. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/migrate.mdCall it with /prompts:migrate. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/migrate.prompt.mdManually: put the files in place
.gemini/commands/migrate.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about migrate
How do I install migrate in Claude Code?
Run /plugin marketplace add serpro69/claude-toolbox, then /plugin install kk@claude-toolbox. The command file ends up at .claude/commands/migrate.md.
What does migrate do?
It shifts task tracking from Task Master MCP to markdown, copying open tasks into /docs/feat/wip/[feature]/tasks.md and then removing the Task Master files and settings.
Do I have to clean anything up myself?
Yes: the task-master-ai entry under mcpServers in ~/.claude.json is user-level config, so you delete it by hand. Without a connected MCP server the tasks are read from .taskmaster/tasks/tasks.json instead.