sdd:tasks

Shared Instructions

• Transition Logging — append a transition entry on every .spec-context.json write

Steps

1. Load Context

If $ARGUMENTS is provided, use specs/{$ARGUMENTS}/ as the target directory. Otherwise, find the most recently modified directory under specs/ that contains both spec.md and plan.md.

Read in parallel:

• specs/{NNN}-{slug}/spec.md — feature name, requirements, scenarios
• specs/{NNN}-{slug}/plan.md — approach, files to create/modify
• specs/{NNN}-{slug}/.spec-context.json — current step/task (if exists)

If no spec/plan found, stop: "Run /sdd:specify and /sdd:plan first."

Update specs/{NNN}-{slug}/.spec-context.json and append a transition entry per transition-logging:

{ "currentStep": "tasks", "currentTask": null, "progress": "loading", "next": "implement", "updated": "{TODAY}" }

---

2. Write specs/{NNN}-{slug}/tasks.md

Update specs/{NNN}-{slug}/.spec-context.json — set progress to "writing-tasks" and append a transition entry per transition-logging.

Read lib/templates/tasks.md, fill placeholders ({Feature Name}, {TODAY}), generate tasks based on the plan's file list, and write to specs/{NNN}-{slug}/tasks.md.

Phase rules:

• Phase 1: all core implementation tasks ordered by dependency (T001, T002, ...).
• Mark a task [P] when it (a) touches files that no other task in its parallel group touches AND (b) has no data dependency on its siblings in the group. Two tasks that modify the same file are never both [P].
• Consecutive [P] tasks form a parallel group that /sdd:implement runs as a batch of concurrent subagents. A task without [P] acts as a gate — it waits for everything above it.
• After listing tasks, do a parallelism pass: group tasks by file path. Any task whose file appears nowhere else in Phase 1 (and has no data dep on siblings) is a [P] candidate. A 5+ task spec with zero [P] markers should be reviewed before completing — that almost always means a missed pass.
• When two interpretations are both legal, prefer the one with more [P] markers. Sequential is the safe-but-slow fallback, not the default.