Resolves approved todos in parallel, documents lessons learned, and cleans up completed files.
npx skills add https://github.com/mmnavarr/harness --skill todo-resolve-mmnavarr
Please help me install this Agent Skill. Skill: todo-resolve Source: https://github.com/mmnavarr/harness/tree/main/skills/todo-resolve Command: npx skills add https://github.com/mmnavarr/harness --skill todo-resolve-mmnavarr
.context/compound-engineering/todos/ and legacy todos/ directories, resolving only ready todos while skipping and reporting pending ones. - Parallel batch execution: Spawns a resolver agent per todo, batching large sets into groups of four with short status summaries to keep context manageable. - Lessons-learned capture: Loads the compound skill after resolution to document patterns and architectural insights in docs/solutions/. - Use Case: After running a code review that produced eight approved fix todos, invoke this Skill to resolve them in parallel, commit the changes, record what was learned, and delete the completed todo files. ## Quick Start Resolve all ready todos from the latest review session and document any lessons learned.High-intent search queries and answers about installing and using this skill.
Run the todo-resolve workflow, which scans todo directories for ready-status items, plans them by dependency, and spawns parallel resolver agents. It commits changes, documents lessons learned, and deletes completed todo files.
The planning step analyzes dependencies and runs items that others depend on first, outputting a mermaid diagram of execution order. Parallel execution falls back to sequential when dependency order requires it.
Pending todos are skipped entirely since they have not been triaged. At the end of the run they are listed so you know what was left behind and can approve them with a triage pass.
Yes, pass a specific todo ID or pattern as an argument to filter the scan to matching todos only. The filtered todos must still have ready status to be resolved.
Todos recommending deletion or gitignoring of files in docs/brainstorms/, docs/plans/, or docs/solutions/ are intentionally skipped because those files are deliberate pipeline artifacts, not cleanup targets.
ybbms777Resolve batch-approved todos in parallel and capture lessons via ce:compound.
petekpCapture conversation learnings into project knowledge files and cross-project patterns.
michaelvolzTriage pending todo findings by severity and readiness status.
jikig-aiAnalyze dependency order and spawn parallel resolver agents for TODO comments.