Work

Work on a backlog task and its subtasks sequentially

arsfeld 1 updated 6mo ago
Claude CodeGeneric
View source ↗
---
description: Work on a backlog task and its subtasks sequentially
argument-hint: <task-id>
---

# Work Backlog Task: $ARGUMENTS

You are working on a backlog task. Follow this workflow EXACTLY.

## Step 1: Load the Parent Task

Use `mcp__backlog__task_view` to load the task with ID: `$ARGUMENTS`

If the task doesn't exist, inform the user and stop.

## Step 2: Search for ALL Subtasks

**CRITICAL**: You MUST search for ALL subtasks of this parent task.

Use `mcp__backlog__task_list` with appropriate filters, or use `mcp__backlog__task_search` to find tasks that reference this parent task ID.

Search strategies:
1. Search by parent task ID in the task list
2. Search for tasks that mention the parent task ID in their description or dependencies

## Step 3: Present High-Level Overview

Present a clear overview to the user:

Task Overview: [Parent Task Title]

Status: [status] Priority: [priority] Description: [description summary]

Subtasks ([count] total):

# ID Title Status Priority
1 ... ... ... ...

Progress: [X/Y completed]


**Immediately proceed to start working** - do NOT ask for confirmation.

## Step 4: Select Next Subtask to Work On

Select the next subtask using this priority order:

1. **First**: Any subtask with status "In Progress" (continue unfinished work)
2. **Then**: Subtasks with status "To Do", ordered by:
   - Priority: high > medium > low
   - If same priority, take the first one by order

If ALL subtasks are "Done", check if the parent task can be marked complete.

If there are NO subtasks, work on the parent task directly.

## Step 5: Work on the Selected Task

Before starting work:
1. Update the task status to "In Progress" using `mcp__backlog__task_edit`
2. Read the task's implementation plan and notes if any exist

While working:
- Follow the acceptance criteria as your checklist
- Update implementation notes as you make progress using `mcp__backlog__task_edit` with `notesAppend`
- Check off acceptance criteria as you complete them using `acceptanceCriteriaCheck`

## Step 6: Complete the Subtask

When the subtask is done:
1. Verify ALL acceptance criteria are met
2. Mark remaining acceptance criteria as checked
3. Update status to "Done" using `mcp__backlog__task_edit`
4. Add final implementation notes summarizing what was done

## Step 7: Continue with Next Subtask

After completing a subtask:
1. Return to Step 4 to select the next subtask
2. Continue until all subtasks are complete or you need user input

## Step 8: Complete Parent Task

When all subtasks are done:
1. Review the parent task's acceptance criteria
2. Mark the parent task as "Done" if all criteria are met
3. Add summary notes to the parent task

## Important Guidelines

- **Always search thoroughly**: Don't assume you know all subtasks - search the backlog
- **Keep backlog updated**: Status changes, notes, and acceptance criteria must stay current
- **Work sequentially**: Complete one subtask before starting the next
- **Ask for clarification**: If a task is unclear, ask the user before proceeding
- **Commit incrementally**: Make commits as you complete meaningful chunks of work
- **Document blockers**: If blocked, add notes explaining why and what's needed

## Backlog Update Commands Reference

Update status

mcp__backlog__task_edit(id: "...", status: "In Progress") mcp__backlog__task_edit(id: "...", status: "Done")

Add implementation notes (append)

mcp__backlog__task_edit(id: "...", notesAppend: ["Note about progress..."])

Check acceptance criteria (by index, 1-based)

mcp__backlog__task_edit(id: "...", acceptanceCriteriaCheck: [1, 2, 3])

Set implementation plan

mcp__backlog__task_edit(id: "...", planSet: "## Plan\n1. Step one\n2. Step two")


Now begin by loading task `$ARGUMENTS` and discovering all its subtasks.

Maintain Work?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[Work on getagentictools](https://getagentictools.com/loops/arsfeld-work-backlog-task-arguments?ref=badge)