implement-task

Orchestrate planned tasks from todos.md with a parallel agent team.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/danielmichaels/cskills --skill implement-task-danielmichaels
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-task
Source: https://github.com/danielmichaels/cskills/tree/main/go/skills/implement-task
Command: npx skills add https://github.com/danielmichaels/cskills --skill implement-task-danielmichaels

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end execution of planned tasks by spawning a team of agents to work on items listed in todos.md, enabling parallel work and support for resumption.

Core Features & Use Cases

  • Spawns an agent team sized to the required parallelism (max 4) and assigns work items from todos.md.
  • Tracks progress, handles state transitions (pending, in_progress, completed), and logs outcomes to log.md.
  • Supports resumption after interruption by resetting in_progress items to pending and preserving completed items.

Quick Start

Initiate execution by selecting the next todo from todos.md and spawning a startup team to work on it.

Frequently Asked Questions about implement-task

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

FAQPage Schema
How do I execute planned tasks in parallel using multiple agents?

To execute tasks in parallel, this Skill spawns a team of up to four agents that work concurrently on items listed in your todos.md file, tracking progress and logging outcomes to log.md.

Can I resume task execution after an interruption without losing completed work?

Yes, resumption is supported by resetting any in_progress items back to pending while preserving all completed items, allowing the agent team to seamlessly continue executing the remaining todos.md tasks.

How does parallel task orchestration handle state transitions and progress logging?

Parallel task orchestration manages state transitions across pending, in_progress, and completed stages while automatically logging execution outcomes and progress updates to log.md within a git worktree context.

What is the maximum number of parallel agents I can spawn for task execution?

The maximum parallelism limit for spawning an agent team to execute todos.md items is four concurrent agents, with optional gating available between parallel groups to control workflow progression.

Do I need a git worktree to orchestrate parallel agent task execution?

A git worktree context is required for orchestrating parallel agents, as the task execution mechanism operates within this environment to safely manage state transitions, handle failures, and monitor progress.

How does the task execution workflow handle agent failures during parallel processing?

The task execution workflow handles failures by monitoring agent progress during parallel processing, enforcing prerequisites, and managing state transitions to ensure failed items can be resumed or re-attempted from their pending state.