How do I install the Todo Resolve skill?

Run npx skillmds add udecode/todo-resolve in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Todo Resolve safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Todo Resolve?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Todo Resolve free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Todo Resolve?

udecode (@udecode) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Todo Resolve by udecode — Agent Skill

Name: Todo Resolve
Rating: 4.2 (5 reviews)
Author: udecode

File contents

Resolve approved todos using parallel processing, document lessons learned, then clean up.

Only ready todos are resolved. pending todos are skipped — they haven't been triaged yet. If pending todos exist, list them at the end so the user knows what was left behind.

Workflow

1. Analyze

Scan .context/compound-engineering/todos/*.md and legacy todos/*.md. Partition by status:

ready (status field or -ready- in filename): resolve these.
pending: skip. Report them at the end.
complete: ignore, already done.

If a specific todo ID or pattern was passed as an argument, filter to matching todos only (still must be ready).

Residual actionable work from ce:review mode:autofix after its safe_auto pass will already be ready.

Skip any todo that recommends deleting, removing, or gitignoring files in docs/brainstorms/, docs/plans/, or docs/solutions/ — these are intentional pipeline artifacts.

2. Plan

Create a task list grouped by type (e.g., TaskCreate in Claude Code, update_plan in Codex). Analyze dependencies -- items that others depend on run first. Output a mermaid diagram showing execution order and parallelism.

3. Implement (PARALLEL)

Spawn a compound-engineering:workflow:pr-comment-resolver agent per item. Prefer parallel; fall back to sequential respecting dependency order.

Batching: 1-4 items: direct parallel returns. 5+ items: batches of 4, each returning only a short status summary (todo handled, files changed, tests run/skipped, blockers).

For large sets, use a scratch directory at .context/compound-engineering/todo-resolve/<run-id>/ for per-resolver artifacts. Return only completion summaries to parent.

4. Commit & Resolve

Commit changes, mark todos resolved, push to remote.

GATE: STOP. Verify todos resolved and changes committed before proceeding.

5. Compound on Lessons Learned

Load the ce:compound skill to document what was learned. Todo resolutions often surface patterns and architectural insights worth capturing.

GATE: STOP. Verify the compound skill produced a solution document in docs/solutions/. If none (user declined or no learnings), continue.

6. Clean Up

Delete completed/resolved todo files from both paths. If a scratch directory was created at .context/compound-engineering/todo-resolve/<run-id>/, delete it (unless user asked to inspect).

Todos resolved: [count]
Pending (skipped): [count, or "none"]
Lessons documented: [path to solution doc, or "skipped"]
Todos cleaned up: [count deleted]

If pending todos were skipped, list them:

Skipped pending todos (run /todo-triage to approve):
  - 003-pending-p2-missing-index.md
  - 005-pending-p3-rename-variable.md

---name: todo-resolvedescription: Use when batch-resolving approved todos, especially after code review or triage sessions--- Resolve approved todos using parallel processing, document lessons learned, then clean up. Only `ready` todos are resolved. `pending` todos are skipped — they haven't been triaged yet. If pending todos exist, list them at the end so the user knows what was left behind. ## Workflow ### 1. Analyze Scan `.context/compound-engineering/todos/*.md` and legacy `todos/*.md`. Partition by status: - **`ready`** (status field or `-ready-` in filename): resolve these. - **`pending`**: skip. Report them at the end. - **`complete`**: ignore, already done. If a specific todo ID or pattern was passed as an argument, filter to matching todos only (still must be `ready`). Residual actionable work from `ce:review mode:autofix` after its `safe_auto` pass will already be `ready`. Skip any todo that recommends deleting, removing, or gitignoring files in `docs/brainstorms/`, `docs/plans/`, or `docs/solutions/` — these are intentional pipeline artifacts. ### 2. Plan Create a task list grouped by type (e.g., `TaskCreate` in Claude Code, `update_plan` in Codex). Analyze dependencies -- items that others depend on run first. Output a mermaid diagram showing execution order and parallelism. ### 3. Implement (PARALLEL) Spawn a `compound-engineering:workflow:pr-comment-resolver` agent per item. Prefer parallel; fall back to sequential respecting dependency order. **Batching:** 1-4 items: direct parallel returns. 5+ items: batches of 4, each returning only a short status summary (todo handled, files changed, tests run/skipped, blockers). For large sets, use a scratch directory at `.context/compound-engineering/todo-resolve/<run-id>/` for per-resolver artifacts. Return only completion summaries to parent. ### 4. Commit & Resolve Commit changes, mark todos resolved, push to remote. GATE: STOP. Verify todos resolved and changes committed before proceeding. ### 5. Compound on Lessons Learned Load the `ce:compound` skill to document what was learned. Todo resolutions often surface patterns and architectural insights worth capturing. GATE: STOP. Verify the compound skill produced a solution document in `docs/solutions/`. If none (user declined or no learnings), continue. ### 6. Clean Up Delete completed/resolved todo files from both paths. If a scratch directory was created at `.context/compound-engineering/todo-resolve/<run-id>/`, delete it (unless user asked to inspect). ``` Todos resolved: [count] Pending (skipped): [count, or "none"] Lessons documented: [path to solution doc, or "skipped"] Todos cleaned up: [count deleted] ``` If pending todos were skipped, list them: ``` Skipped pending todos (run /todo-triage to approve): - 003-pending-p2-missing-index.md - 005-pending-p3-rename-variable.md ```

Frequently asked questions