todo-resolve

Resolve ready todos in parallel and report pending items.

50|14|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill todo-resolve-all-the-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-resolve
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/todo-resolve
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill todo-resolve-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-resolving approved todos after code reviews and triage is repetitive and error-prone; this skill automates the workflow end-to-end.

Core Features & Use Cases

  • Analyze and categorize todos by status (ready, pending, complete) across .context/compound-engineering/todos/*.md and legacy todos.
  • Resolve only ready items in parallel, report pending items at the end, and ensure cleanup after completion.
  • Document lessons learned via the ce-compound workflow and keep a clean state by removing resolved todos.

Quick Start

Run the skill to batch-resolve all ready todos in parallel and report pending items.

Frequently Asked Questions about todo-resolve

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

FAQPage Schema
How do I automate batch todo resolution after a code review?

Batch todo resolution scans .context/compound-engineering/todos/*.md and legacy files, filters ready items, and processes them in parallel. It reports pending items at the end and cleans up scratch directories to automate triage workflows.

What is parallel todo triage and how does it work?

Parallel todo triage categorizes items by status across .context/compound-engineering/todos/*.md and legacy files, then concurrently resolves ready items. It uses a per-run scratch directory for artifacts and removes resolved todos to maintain a clean state.

Can I resolve ready and pending todos at the same time during triage?

Pending todos are not resolved during parallel processing. The workflow strictly filters for ready items to act on, while pending items are only collected and reported at the end of the run to prevent processing errors.

Does todo-resolve work with legacy todo files or only markdown formats?

The workflow supports both .context/compound-engineering/todos/*.md and legacy todo formats. It scans both sources to categorize items by status and resolve ready tasks in parallel during code-review workflows.

What is the best way to clean up resolved todos in a parallel workflow?

Use a per-run scratch directory to store artifacts and remove resolved items after parallel processing. This skill automates that cleanup, ensuring a clean state after resolving ready items during triage.

Why are pending todos reported instead of resolved during batch processing?

Pending todos lack the ready status required for safe parallel execution. Reporting them at the end highlights items needing further attention or dependencies before they can be acted on during code-review workflows.