From 15af65e75b83af49108605a9bb26c5cddccdf49a Mon Sep 17 00:00:00 2001 From: vam Date: Sat, 5 Sep 2026 11:40:39 +0800 Subject: [PATCH] docs(spec): clarify external artifact ownership --- skills/spec-driven-development/SKILL.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/skills/spec-driven-development/SKILL.md b/skills/spec-driven-development/SKILL.md index f3f5877c..cadc9213 100644 --- a/skills/spec-driven-development/SKILL.md +++ b/skills/spec-driven-development/SKILL.md @@ -147,6 +147,12 @@ Don't silently fill in ambiguous requirements. The spec's entire purpose is to s [Anything unresolved that needs human input] ``` +**External spec tools:** This workflow is format-agnostic. If the project +already uses OpenSpec or another specification system, keep that system's +artifact format and storage conventions instead of creating a duplicate +`SPEC.md`. This skill owns the clarification, content, and approval gates; the +external tool owns how the approved spec is represented. + **Reframe instructions as success criteria.** When receiving vague requirements, translate them into concrete conditions: ```