summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAddy Osmani <addyosmani@gmail.com>2026-11-18 12:04:51 -0800
committerGitHub <noreply@github.com>2026-11-18 12:04:51 -0800
commitd7fd10362675f8829b78e5e031fd57e6e9e9cae7 (patch)
tree4a9758f83e59dc5bdf2338d0474e8fba0371d2cf
parent49d7b464f38c585449f12414008b40904986976f (diff)
parentb8bea427a250508295fdf5884e3375ecc24870a5 (diff)
Merge #797: save capability map and module specs under spec/
fix: save capability map and module specs under spec/
-rw-r--r--scripts/validate-artifact-paths-test.js8
-rw-r--r--skills/spec-driven-development/SKILL.md2
2 files changed, 9 insertions, 1 deletions
diff --git a/scripts/validate-artifact-paths-test.js b/scripts/validate-artifact-paths-test.js
index f79c64f..9a69fe2 100644
--- a/scripts/validate-artifact-paths-test.js
+++ b/scripts/validate-artifact-paths-test.js
@@ -191,3 +191,11 @@ test('guards the Copilot setup doc, whose prompt-file aliases name the artifacts
assert.match(result.stdout, /docs\/copilot-setup\.md/);
assert.match(result.stdout, /specs\/\[name\]\/spec\.md/);
});
+
+test('spec-driven-development saves the capability map and module specs under spec/, not the project root', () => {
+ const skill = fs.readFileSync(path.join(__dirname, '..', 'skills', 'spec-driven-development', 'SKILL.md'), 'utf8');
+
+ assert.match(skill, /spec\/capability-map\.md/);
+ assert.match(skill, /spec\/SPEC-identity\.md/);
+ assert.doesNotMatch(skill, /at the project root and each module/);
+});
diff --git a/skills/spec-driven-development/SKILL.md b/skills/spec-driven-development/SKILL.md
index 927c79d..b96b9f7 100644
--- a/skills/spec-driven-development/SKILL.md
+++ b/skills/spec-driven-development/SKILL.md
@@ -62,7 +62,7 @@ Build order: identity → billing, notifications → reporting
**The map is gated like every phase.** The human reviews module boundaries, dependency direction, and build order before any module spec is written. Getting the map wrong is expensive; reviewing ten lines is not.
-**Then recurse per module.** Run Specify → Plan → Tasks → Implement for each module in dependency order. Each module gets its own spec, scoped to that module's objective, boundaries, and success criteria. Save the approved map at the project root and each module's spec alongside it, named by module id (`SPEC-identity.md`, `SPEC-billing.md`) — the map, not filename guessing, is the index of what exists.
+**Then recurse per module.** Run Specify → Plan → Tasks → Implement for each module in dependency order. Each module gets its own spec, scoped to that module's objective, boundaries, and success criteria. Save the approved map as `spec/capability-map.md` and each module's spec alongside it in `spec/`, named by module id (`spec/SPEC-identity.md`, `spec/SPEC-billing.md`) — `/build` already accepts specs under `spec/`, and the root stays uncluttered — the map, not filename guessing, is the index of what exists.
### Phase 1: Specify