spec:do-all

Execute pending tasks from a specification's tasks.md with parallel subtasks.

1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/IKatsuba/skills --skill spec-do-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec:do-all
Source: https://github.com/IKatsuba/skills/tree/main/spec/do-all
Command: npx skills add https://github.com/IKatsuba/skills --skill spec-do-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate execution of all pending tasks from a specification's tasks document, ensuring major tasks run sequentially while enabling parallel subtasks when safe.

Core Features & Use Cases

  • Orchestrates end-to-end execution of specs from .specs/<spec-name>/ directories, respecting task dependencies between major tasks and subtasks.
  • Supports parallel execution of independent subtasks within a major task, with safeguards and progress tracking.
  • Automatically updates task status and can trigger commit workflows after completion.

Quick Start

Provide the spec name to execute all remaining tasks defined in its tasks.md, applying parallelism where safe.

Frequently Asked Questions about spec:do-all

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

FAQPage Schema
How do I execute all pending tasks from a specification document automatically?

To execute pending tasks automatically, provide the spec name to orchestrate end-to-end execution from the .specs/<spec-name>/tasks.md file, enforcing dependencies and updating task status.

Can I run independent subtasks in parallel while keeping major spec tasks sequential?

Yes, safe parallelism allows independent subtasks within a major task to run in parallel, while major tasks remain sequential to ensure deterministic progress and respect dependencies.

How do I coordinate task execution using requirements, research, and design specs?

Coordinate task execution by reading the requirements.md, research.md, design.md, and tasks.md files within the .specs/<spec-name>/ directory to guide execution and enforce dependencies.

What is the best way to manage workflow automation for spec-driven task lists?

The best way to manage spec-driven workflow automation is using a coordinator that reads your tasks.md document, applies safe parallelism for independent subtasks, and updates task status automatically.

Does this task automation approach trigger git commit workflows after completion?

Yes, the task automation can trigger commit workflows after completion, automatically updating task status and initiating commit sequences once all pending spec tasks finish executing.

When should I not use parallel execution for spec task management?

You should not use parallel execution for major tasks that must run sequentially, as safe parallelism is restricted to independent subtasks to ensure deterministic progress and dependency enforcement.