Skip to main content
command CX Codex

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

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add serpro69/claude-toolbox
/plugin install kk@claude-toolbox
Open on GitHub

What 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 the tm/ slash commands from a repo
  • drop task-master-ai permissions 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 /migrate and list the open Task Master tasks before writing anything
  • /migrate on this repo, and stop early if there is no .taskmaster/ here
  • Go through /migrate but 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-toolbox

2Manually: put the files in place

.claude/commands/migrate.md

Call it with /migrate. For all projects use ~/.claude/commands/

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.

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set30

The whole set →
isolated The command checks an answer by assigning separate verification questions to isolated sub-agents. Use it to review factual claims or investigate code in a project. CX Codex +1 ★ 155repo stars diff-skill Diffs two revisions of a skill's markdown instructions and flags the edits that weaken a rule or add avoidable complexity. Useful before you accept changes to a skill you rely on. CX Codex +1 ★ 155repo stars isolated Runs an isolated multi-model code review on git changes. Evaluates security, compatibility, and design rules across separate reviewers. CX Codex +1 ★ 155repo stars dependency-handling The dependency-handling skill makes an agent verify dependency details before writing code that uses them. It helps when adding or upgrading a library, API, IaC version, CRD, or container image. CX Codex +1 ★ 155repo stars document Updates project documentation and architectural decisions after delivering a feature or bug fix following profile guidelines. CX Codex +1 ★ 155repo stars clarify-docs clarify-docs revises documentation, pull request drafts, and issue descriptions without changing their intended meaning. Use it when the writing needs clarification rather than implementation. CX Codex +1 ★ 155repo stars profile-resolver profile-resolver — a subagent that reads a diff and the worktree, works out which project profiles are active, and reports which checklists load. Handy when detection has to run apart from the review. CX Codex ★ 155repo stars brainstorm brainstorm guides technical ideation and architecture debates by asking focused questions one at a time before any code gets written. CX Codex +1 ★ 155repo stars

Project sponsors

Companies that keep this analytics open