spec:do-next

Execute the next uncompleted task from a specification's tasks.md file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes the next pending task from a specification's tasks document, enabling incremental progress by automatically identifying and starting the first incomplete item for a given spec.

Core Features & Use Cases

  • Automatically finds the first pending or in-progress task in .specs/<spec-name>/tasks.md
  • Coordinates subtasks, updates tasks.md, and delegates execution to a subagent for complex steps
  • Provides auditability through progress commits and supports review cycles between subtasks

Quick Start

Invoke the next pending task for a spec by running /spec:do-next <spec-name>.

Frequently Asked Questions about spec:do-next

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

FAQPage Schema
How do I automatically execute the next pending task from a specification checklist?

To execute the next pending task from a specification, this Skill scans your tasks.md file, identifies the first incomplete checkbox, and delegates the work to a subagent. It updates the checklist and commits the progress to git for traceability.

How does incremental workflow automation handle subtasks in a markdown specification?

Incremental workflow automation handles subtasks by parsing the markdown checklist, executing the next uncompleted item via a subagent, and tracking progress. It supports both major tasks and subtasks by updating the document after each step.

Can I use git commits to track task execution progress in a spec-driven workflow?

Yes, you can use git commits to track task execution progress. This Skill integrates with git to commit each change automatically after a pending task or subtask is completed, providing an auditable history of your incremental workflow.

What is the required file structure for executing tasks from a specification document?

The required file structure organizes work under .specs/<spec-name>/tasks.md. You must use this path with markdown checkboxes for each subtask so the automation can correctly identify, execute, and update pending items.

Do I need a subagent to run complex subtasks from my specification checklists?

Yes, a subagent is used to run complex subtasks from your specification checklists. When the automation identifies an incomplete item in tasks.md, it delegates the execution to a subagent to handle the detailed work and updates the checklist upon completion.