From 45d05d75363abf13f99d09e899d61e07b8010685 Mon Sep 17 00:00:00 2001 From: Nick Baumann Date: Fri, 1 May 2026 09:34:51 -0500 Subject: [PATCH] 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 --- skills/.curated/migrate-to-codex/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/.curated/migrate-to-codex/SKILL.md b/skills/.curated/migrate-to-codex/SKILL.md index f892d99..b1c001b 100644 --- a/skills/.curated/migrate-to-codex/SKILL.md +++ b/skills/.curated/migrate-to-codex/SKILL.md @@ -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