spec:do-task

Executes a specific task by number from a specification's tasks document.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes a specific task by its number from a specification's tasks document. This skill allows targeted execution of any task in the plan.

Core Features & Use Cases

  • Targeted execution of a specific task by number from a specification's tasks document.
  • Jump to a particular task, re-run a completed task, or follow non-sequential plan steps.

Quick Start

Run a specific task by its number from the current spec to execute just that subtask.

Frequently Asked Questions about spec:do-task

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

FAQPage Schema
How do I execute a specific task by number from a specification document?

To execute a specific task by number, the skill locates the target task within the specification's tasks document and launches a subagent to perform the selected subtasks on demand. It updates the tasks state automatically.

Can I re-run a completed task or jump to non-sequential plan steps in my workflow?

Yes, you can re-run a completed task or follow non-sequential plan steps. Targeted execution allows you to jump to any particular task by its number from the specification document on demand.

How do I run a specific subtask from the .specs directory structure?

You run a specific subtask by providing its task number. The skill reads the spec's documents under .specs/<spec-name>/, locates the target task, updates the tasks.md state, and executes it.

Does targeted task execution update the tasks.md state file automatically?

Yes, targeted task execution updates the tasks.md state file automatically. When the skill locates the target task by its number, it modifies the state document before launching the subagent for execution.

What is the best way to execute non-sequential specification tasks in development automation?

The best way to execute non-sequential specification tasks is using targeted task execution by number. It locates the exact subtask in the tasks document and launches a dedicated subagent to perform it.