Execute Specific Task

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

When to use

Use this skill when the user needs to:

• •Execute a specific task out of order
• •Re-run a previously completed task
• •Jump to a particular task in the implementation plan

Specification Files Structure

All specification documents are located in .specs/<spec-name>/ directory:

Always read all three files to understand the full context before executing tasks.

Instructions

Step 1: Parse Arguments

The <args> should contain:

• •Task number (required) - e.g., "1", "1.2", "3.1"
• •Spec name (optional) - e.g., "user-auth"

Format examples:

• •spec:do-task 1.2 - Execute task 1.2 from the current/only spec
• •spec:do-task user-auth 2.1 - Execute task 2.1 from the user-auth spec
• •spec:do-task 3 - Execute major task 3 (and all its subtasks)

Step 2: Locate and Read Specification Documents

1. •If spec name provided, look in .specs/<spec-name>/
2. •If no spec name, check if there's only one spec in .specs/
3. •If multiple specs exist without a name specified, list them and ask user to choose
4. •Read and parse all specification documents:
   • •requirements.md - understand what needs to be built
   • •design.md - understand how it should be built
   • •tasks.md - get the list of tasks to execute

Step 3: Find the Specified Task

1. •Search for the task matching the provided number
2. •If task number is a major task (e.g., "2"), include all subtasks (2.1, 2.2, etc.)
3. •If task not found, list available tasks and ask for correction

Step 4: Execute the Task

IMPORTANT: Each subtask is executed as a separate subagent and committed independently. Do NOT group subtasks into a single agent or commit.

If the task number points to a subtask (e.g., "1.2"):

1. •Mark subtask as in-progress - Update the subtask checkbox to [-] in tasks.md
2. •Show task info - Display to the user:
   • •Subtask number and description
   • •Files to create/modify
   • •Requirements being addressed
   • •Current status (pending/in-progress/completed)
3. •Launch subagent - Use the Task tool with subagent_type: "general-purpose" to execute the subtask:
   • •Provide the full subtask description, file paths, and requirements
   • •Include relevant context from the spec (requirements.md, design.md)
4. •Verify result - Review the subagent's output for success
5. •Mark subtask as complete - Update the subtask checkbox to [x] in tasks.md
6. •Commit the changes - Use the git:commit skill to commit (see Committing Changes section)
7. •If all subtasks of the parent major task are now complete, mark the major task as [x] in tasks.md and commit this change using the git:commit skill

Step 5: Handle Major Tasks with Subtasks

If the task number points to a major task (e.g., "2") that has subtasks:

1. •Iterate over each subtask in order
2. •For each subtask, follow the subtask execution flow from Step 4 (separate subagent + separate commit per subtask)
3. •Mark the major task as [x] in tasks.md and commit this change using the git:commit skill

Step 6: Report Completion

After completing the task:

1. •Summarize what was implemented
2. •Note if this was a re-execution of a completed task
3. •Show related tasks that might need attention

Committing Changes

After completing each subtask, commit using the git:commit skill:

1. •Stage the changed files related to the subtask
2. •Invoke the git:commit skill — it will analyze staged changes, determine the commit type, and create a properly formatted Conventional Commits message

Skip committing if:

• •The user explicitly asked not to commit
• •The subtask only modified the tasks.md file (checkpoint tasks)

Warning on Dependencies

If the specified task depends on incomplete prerequisite tasks:

1. •Warn the user about missing dependencies
2. •List the prerequisite tasks
3. •Ask if they want to:
   • •Execute prerequisites first
   • •Proceed anyway
   • •Cancel

Error Handling

• •If the task fails, keep it marked as [-]
• •Report the issue to the user
• •Suggest fixes or ask for guidance

Arguments

• •<args> - Task number and optionally spec name
  • •Format: [spec-name] <task-number>
  • •Task number: "1", "1.2", "2.3.1", etc.
  • •Spec name: kebab-case identifier

Examples:

• •1.2 - Task 1.2 from the default/only spec
• •user-auth 3.1 - Task 3.1 from user-auth spec
• •payment-flow 2 - All of task 2 from payment-flow spec