Spec Update FAQs

Question 1

Does this skill support both Markdown and YAML?

Accepted Answer

Yes, Spec Update is designed to parse and update both standard Markdown spec files (using checkboxes or lists) and structured tasks.yaml files used for project tracking.

Question 2

How does Spec Update determine if a task is actually finished?

Accepted Answer

The skill analyzes git commit messages for task references, checks if files mentioned in the spec were modified or created, and verifies if the project baseline has changed significantly since the task was defined.

Question 3

Can I manually override the automated status detection?

Accepted Answer

Yes, you can use the --context argument to provide manual overrides, clarifications, or notes about blockers that take precedence over the automatic git analysis.

Question 4

What is the difference between status and content modes?

Accepted Answer

Status mode only updates completion checkboxes and metadata, while Content mode can add new tasks, remove obsolete ones, or restructure the spec based on what was learned during development.

Question 5

Will Spec Update change my source code files?

Accepted Answer

No, the skill only modifies specification documents and task tracking files. It reads your source code and git history as evidence but does not perform code refactoring.

Spec Update

Key Features

Use Cases

Spec Update

Key Features

Use Cases