SDD Progress Tracker FAQs

Question 1

When should I use sdd-update instead of sdd-modify?

Accepted Answer

Use sdd-update for lightweight metadata changes like marking a task as in-progress or completed and adding journal entries. Use sdd-modify for heavyweight structural changes, such as adding or removing tasks, updating task descriptions, or applying review feedback.

Question 2

Does this skill support automated verification testing?

Accepted Answer

Yes. The skill can record manual verification results or automatically execute tests defined in task metadata. It features configurable failure handling, such as automatic retries or status reverts if a verification check fails.

Question 3

Why shouldn't I use standard Bash commands to read spec files?

Accepted Answer

Spec-Driven Development files can be large (50KB+). Using the sdd CLI commands included in this skill is more context-efficient than using 'cat' or 'Read()', as it provides structured access that avoids wasting Claude's context window tokens.

Question 4

How does the atomic task completion feature work?

Accepted Answer

By using the 'complete-task' command, the skill atomically marks a task as completed and prompts for a journal entry simultaneously. This ensures documentation never lags behind implementation and automatically handles journaling for parent phases and groups.

Question 5

What is the SDD Progress Tracker skill for Claude Code?

Accepted Answer

The SDD Progress Tracker (sdd-update) is a specialized Claude Code skill designed to manage the administrative aspects of Spec-Driven Development. It handles task status updates, decision journaling, blocker tracking, and moving specifications through their lifecycle folders.

SDD Progress Tracker

SDD Progress Tracker

Key Features

Use Cases

Key Features

Use Cases