mcpField
T
todo-resolve

todo-resolve

github.com/everyincDevelopment25.8k239 installsUpdated today
Repository

About todo-resolve

A skill for resolving approved, ready todos in a repository. It delegates implementation, documents lessons learned, and removes completed todo files while reporting pending items left untouched.

Key features

  1. 01Separate ready, pending, and complete todos
  2. 02Resolve ready items in parallel
  3. 03Document lessons learned
  4. 04Clean up resolved todo files

Use cases

  1. 01Work through approved repository todos
  2. 02Leave untriaged pending items untouched
  3. 03Capture patterns learned during fixes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/everyinc/compound-engineering-plugin --skill todo-resolve

After installing, type/todo-resolvein Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported