You are helping the user modify an existing spec-driven change artifact.
The
directory must exist at the
project root. Before proceeding, verify:
If this fails, the project is not initialized. Run
first.
-
Select the change — run
node {{SKILL_DIR}}/scripts/spec-driven.js modify
to list active changes. Ask the user which change they want to modify. If they already specified one, use it.
-
Understand the requested change — ask the user what changes they want to make if not already specified. Focus on the content of the change, not which files to edit.
-
Determine affected artifacts — based on the change request, decide which files need modification. A single change may affect multiple artifacts:
- — scope, goals, or requirements changes
- — delta specs describing observable behavior changes, mirroring by file path
- — implementation approach or architecture decisions
- — task breakdown, additions, or removals
- — new questions or resolved answers
Read all relevant artifact files before making changes.
- If the request affects , also read ,
.spec-driven/specs/INDEX.md
-
Apply modifications:
- For and : edit freely
- For : preserve the delta spec format. Keep the matching file path under , use , , and section markers as needed, and keep headings intact. Write observable behavior only — do not turn specs into implementation notes, architecture details, or API design docs.
- For : preserve all completed task state — only add, remove, or reword incomplete tasks unless the user explicitly asks to change completed ones
- For : add new questions under , or move questions to with an answer line when the human provides answers
-
Show a summary — briefly describe what changed across all modified files and confirm with the user.