todo-resolve

Resolves approved todo items in parallel and documents lessons learned.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Jerrylalala/compound-engineering --skill todo-resolve-jerrylalala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: todo-resolve
Source: https://github.com/Jerrylalala/compound-engineering/tree/main/plugins/compound-engineering/skills/todo-resolve
Command: npx skills add https://github.com/Jerrylalala/compound-engineering --skill todo-resolve-jerrylalala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After code reviews or triage sessions, approved todos pile up and resolving them one by one is slow and error-prone. This Skill batch-resolves all ready todos with parallel agents, commits the changes, and captures lessons learned. ## Core Features & Use Cases - Status-aware triage: Scans todo files and partitions them by status, resolving only ready items while reporting skipped pending ones. - Parallel resolution: Spawns a resolver agent per todo, batching large sets into groups of four with dependency-aware ordering and a mermaid execution diagram. - Knowledge capture: Commits changes, marks todos resolved, then runs the compound workflow to document patterns in docs/solutions/ before cleaning up resolved files. - Use Case: After a ce:review session leaves eight approved fix todos, run this Skill to resolve them in parallel batches, commit the fixes, and record the architectural insights discovered. ## Quick Start Resolve all ready todos from the latest review session and document any lessons learned.

Frequently Asked Questions about todo-resolve

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I batch-resolve todos after a code review?▼

Run the todo-resolve skill, which scans todo files for ready-status items and spawns a parallel resolver agent per item. It commits the changes, marks todos resolved, and cleans up completed files automatically.

What happens to pending todos during batch resolution?▼

Pending todos are skipped because they have not been triaged yet. The skill lists them at the end of the run so you know what was left behind and can approve them with todo-triage first.

How does parallel todo resolution handle dependencies?▼

The skill analyzes dependencies during planning and runs items others depend on first. Sets of five or more are processed in batches of four, with each batch returning only a short status summary.

Can I resolve only a specific todo instead of all of them?▼

Yes, pass a specific todo ID or pattern as an argument to filter the matching todos. The filtered items must still have ready status to be resolved.

Why are some todos about deleting docs files skipped?▼

Todos recommending deletion or gitignoring of files in docs/brainstorms, docs/plans, or docs/solutions are intentionally skipped. Those files are deliberate pipeline artifacts of the compound engineering workflow.