Spec-Driven Development Modification FAQs

Question 1

How does sdd-modify ensure specification changes are safe?

Accepted Answer

The skill follows a 'safe systematic changes' philosophy, utilizing dry-run previews, automatic backups in a dedicated directory, and immediate validation after every application. If validation fails, the skill can roll back to the previous state.

Question 2

What happens if a modification breaks the specification schema?

Accepted Answer

The tool automatically validates the result after every application. If issues are found, it provides an 'auto-fix' action or uses its backup system to restore the spec to its last known valid state.

Question 3

Does this skill edit files directly using shell commands?

Accepted Answer

No. For safety and consistency, the skill exclusively uses the Foundry MCP server tools to interact with specs, avoiding raw shell commands like cat or jq.

Question 4

Can I use sdd-modify to mark tasks as completed?

Accepted Answer

No. sdd-modify is specifically for structural changes like updating descriptions or adding tasks. To update task status or mark items as completed, you should use the sdd-update skill.

Question 5

How does it handle feedback from markdown review files?

Accepted Answer

The skill includes a 'parse-feedback' action via the Foundry MCP that converts markdown-based review findings into a structured modification JSON, which can then be previewed and applied.

Spec-Driven Development Modification

Características Principales

Casos de Uso

Spec-Driven Development Modification

Características Principales

Casos de Uso