todo-resolve

Batch-resolve approved todos, document lessons learned, and clean up completed items.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill todo-resolve-mukles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-resolve
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/todo-resolve
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill todo-resolve-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates batch resolution of approved todos, documenting lessons learned and cleaning up artifacts.

Core Features & Use Cases

  • Parallel resolution of ready todos from code review triage.
  • Reporting of pending todos and gating to ensure only ready items are processed.
  • Documentation of lessons learned and cleanup of resolved items to maintain repo hygiene.

Quick Start

Run the todo-resolve skill to process all ready todos from the designated directories and generate a summary of results.

Frequently Asked Questions about todo-resolve

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

FAQPage Schema
How do I automate todo resolution and cleanup for code review triage?

Automated todo resolution batch-processes approved items in parallel, documents lessons learned, and removes completed artifacts to maintain repository hygiene. It skips pending items and enforces verification gates before committing changes.

What is the best way to batch-resolve approved todos while skipping pending ones?

Batch-resolving approved todos is handled by processing only ready items in parallel with per-item agents. Pending todos are automatically skipped and reported, ensuring only gated and verified changes are committed to the repository.

Can I filter todo resolution by a specific todo ID or pattern?

Filtering todo resolution by a specific ID or pattern is supported as an optional parameter during the batch process. This allows targeted resolution of specific ready items while still enforcing verification gates before committing.

How does parallel processing work when resolving todos from local directories?

Parallel todo resolution deploys per-item agents to process ready todos simultaneously from local .context/compound-engineering/todo-resolve and legacy todo files. It enforces gates to verify changes before committing and reports any pending items skipped.

Why does todo resolution require access to .context/compound-engineering directories?

Todo resolution requires access to local .context/compound-engineering/todo-resolve and legacy todo files to identify ready items for batch processing. This directory structure provides the source todos and ensures lessons learned are documented and artifacts cleaned up.