todo-resolve

Resolve ready todo items in compound engineering repositories.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill todo-resolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-resolve
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/todo-resolve
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill todo-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates clearing ready todos after review or triage so pending work stays highlighted and completed tasks no longer clutter the backlog.

Core Features & Use Cases

  • Status-aware scanning: Ingests .context/compound-engineering/todos/*.md and legacy todos/*.md, resolving only entries marked ready while listing any pending items for later attention.
  • Structured execution plan: Groups tasks by type, analyzes dependencies, and outputs a mermaid diagram to visualize execution order and parallelism requirements.
  • Parallel implementation and cleanup: Spawns resolver agents for each item (with batching for large runs), commits resolutions, documents lessons with the ce:compound skill, and removes completed todo files along with any scratch artifacts.

Quick Start

Ask todo-resolve to clear all ready todos after your review session.

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 approved todos after a code review session?

Batch resolving approved todos involves scanning `.context/compound-engineering/todos` and legacy `todos` files for entries marked ready, then spawning parallel resolver agents to clear them while skipping pending items.

What is the best way to clear ready todos while keeping pending items highlighted?

Clearing ready todos while keeping pending items highlighted requires status-aware scanning that resolves only entries marked ready, lists pending items for later attention, and removes completed todo files along with scratch artifacts.

Can I filter which ready todos get resolved by pattern matching?

Yes, you can filter ready todos by an optional pattern during resolution, which allows targeting specific task types or file naming conventions while guaranteeing only ready statuses are processed.

How do I visualize execution order and dependencies for parallel todo resolution?

Visualizing execution order for parallel todo resolution is done by grouping tasks by type, analyzing dependencies, and outputting a mermaid diagram to map parallelism requirements before spawning resolver agents.

Does todo resolution work with both `.context/compound-engineering/todos` and legacy `todos` file formats?

Yes, todo resolution ingests both `.context/compound-engineering/todos/*.md` and legacy `todos/*.md` file formats, scanning them for ready entries while skipping pending files during post-triage or code review batches.

What happens to completed todo files and scratch artifacts after resolution?

After resolution, completed todo files and scratch artifacts are removed during cleanup, and lessons learned are documented with the `ce:compound` skill to keep the backlog uncluttered.