resolve_todo_parallel

Resolve pending CLI TODO comments across multiple files in parallel.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/vib795/copilot-anatomy --skill resolve-todo-parallel-vib795
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve_todo_parallel
Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/resolve_todo_parallel
Command: npx skills add https://github.com/vib795/copilot-anatomy --skill resolve-todo-parallel-vib795

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates resolution of pending CLI TODO comments.

Core Features & Use Cases

  • Parallel resolution of TODO items across multiple files
  • Dependency-aware planning and merging into batch actions
  • Transparent workflow with mermaid diagram outputs for scheduling
  • Safe commits and marking resolved TODOs

Quick Start

Provide an optional TODO ID or pattern to target specific items, then run the workflow to analyze, plan, implement, and commit all pending TODO resolutions in parallel.

Frequently Asked Questions about resolve_todo_parallel

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

FAQPage Schema
How do I automate resolving pending TODO comments across multiple files in parallel?

Parallel TODO resolution automates pending CLI TODO comments by reading unresolved items from /todos, generating a dependency-aware plan, and spawning subagents to implement and commit changes in parallel.

How does dependency-aware planning work for batch resolving TODOs?

Dependency-aware planning analyzes unresolved TODO items, generates a scheduling plan with dependencies, and outputs mermaid diagrams to transparently visualize the parallel resolution workflow before committing changes.

Can I target specific TODO items by ID or pattern for parallel processing?

Yes, you can provide an optional TODO ID or pattern to target specific items, allowing the workflow to analyze, plan, implement, and commit only the matching pending TODO resolutions in parallel.

What is the best way to handle scattered TODO annotations in software projects?

Batch resolving scattered TODO annotations works by reading unresolved items from /todos, skipping artifact todo items, generating dependency-aware plans, and spawning parallel subagents to safely commit all changes.

Does parallel TODO resolution skip artifact todo items automatically?

Yes, parallel TODO resolution automatically skips artifact todo items when reading unresolved TODOs from /todos, ensuring only actionable software annotations are processed and committed by the parallel subagents.

When should I avoid using parallel subagents for CLI todo-management?

Avoid parallel CLI todo-management when TODO items have complex, undocumented interdependencies that cannot be resolved by automated dependency-aware planning, or when safe batch commits are not permitted in your workflow.