Clarify todo completion in migrate-to-codex skill (#383)

**Summary**

- Clarify that the `migrate-to-codex` skill should finish by marking
completed TODO steps as `completed`
- Explicitly prevent a completed migration from leaving a stale
`in_progress` task behind
This commit is contained in:
Nick Baumann
2026-05-01 09:34:51 -05:00
committed by GitHub
parent fb7b56dff0
commit 45d05d7536
+1 -1
View File
@@ -13,7 +13,7 @@ Keep going until the selected migration is completely done: run the migrator, in
Run the migration in this order for each selected global or project source:
1. Start by using Codex's built-in TODO/task list tool. Do not create `MIGRATION_TODOS.md` or any TODO file unless the user explicitly asks. The TODO list input has a `plan` array whose items each have `step` and `status`; use statuses `pending`, `in_progress`, and `completed`. Make the TODOs specific to the selected artifacts. Use literal source → Codex target labels, for example:
1. Start by using Codex's built-in TODO/task list tool. Do not create `MIGRATION_TODOS.md` or any TODO file unless the user explicitly asks. The TODO list input has a `plan` array whose items each have `step` and `status`; use statuses `pending`, `in_progress`, and `completed`. Make the TODOs specific to the selected artifacts. Before finishing, update the TODO list so every finished step is marked `completed` and no step remains `in_progress`. Use literal source → Codex target labels, for example:
- Inspect `.claude/commands` → Codex skills/prompts
- Inspect `.claude/agents``.codex/agents`
- Inspect `.mcp.json``.codex/config.toml` MCP servers