docs: clarify sds.implement creates documents NOT code

Added explicit 'NOT code' clarification to prevent misunderstanding:
- /metaspec.sds.implement writes specification documents
- NOT generating code examples or implementations

Previous confusion:
Users thought it generates code implementation examples, but it actually
creates specification document files (e.g., 002-order.md, 003-payment.md).

Updated locations:
- README.md: 2 places
- AGENTS.md: 3 places
- .metaspec/README.md.j2: 1 place

This ensures clear understanding that the command creates sub-specification
documents, not code files.

Author: NeilJo-GY

AGENTS.md

@@ -149,7 +149,7 @@ For defining domain specifications:
 - `/metaspec.sds.clarify` - Resolve ambiguities in specification
 - `/metaspec.sds.plan` - Plan specification architecture and sub-specifications
 - `/metaspec.sds.tasks` - Break down specification work
-- `/metaspec.sds.implement` - Write specification documents
+- `/metaspec.sds.implement` - Write specification documents (creates sub-spec files, NOT code)
 - `/metaspec.sds.checklist` - Generate quality checklist for specification
 - `/metaspec.sds.analyze` - Check specification consistency
 
@@ -573,7 +573,7 @@ examples/
 /metaspec.sds.specify       # 2. Create root specification
 /metaspec.sds.plan          # 3. Plan sub-specification architecture ⭐
 /metaspec.sds.tasks         # 4. Break down specification tasks ⭐
-/metaspec.sds.implement     # 5. Implement sub-specifications ⭐
+/metaspec.sds.implement     # 5. Write sub-specification documents (NOT code) ⭐
 
 # Quality Assurance (Recommended)
 /metaspec.sds.checklist     # 6. Generate quality checklist
@@ -656,7 +656,7 @@ cd my-speckit
 /metaspec.sds.specify "Define MCP specification"  # Create root specification
 /metaspec.sds.plan  # Plan sub-specification architecture
 /metaspec.sds.tasks  # Break down specification tasks
-/metaspec.sds.implement  # Implement sub-specifications
+/metaspec.sds.implement  # Write sub-specification documents (NOT code)
 /metaspec.sds.checklist  # Quality check (recommended)
 /metaspec.sds.analyze  # Consistency check (recommended)
 

README.md

@@ -289,7 +289,7 @@ cd my-spec-kit
 # /metaspec.sds.specify      - Define specification entities and operations (required)
 # /metaspec.sds.plan         - Plan specification architecture (if complex) ⭐
 # /metaspec.sds.tasks        - Break down specification work (if complex) ⭐
-# /metaspec.sds.implement    - Write specification documents (if complex) ⭐
+# /metaspec.sds.implement    - Write specification documents, NOT code (if complex) ⭐
 # /metaspec.sds.checklist    - Generate quality checklist (recommended)
 # /metaspec.sds.analyze      - Check specification consistency (recommended)
 # /metaspec.sds.clarify      - Resolve specification ambiguities (optional, on-demand)
@@ -389,7 +389,7 @@ pip install -e .
 # If complex (splitting needed):
 # /metaspec.sds.plan          - Plan specification architecture ⭐
 # /metaspec.sds.tasks         - Break down specification work ⭐
-# /metaspec.sds.implement     - Write specification documents ⭐
+# /metaspec.sds.implement     - Write specification documents (NOT code) ⭐
 #
 # Quality (recommended):
 # /metaspec.sds.checklist     - Generate quality checklist

src/metaspec/templates/base/.metaspec/README.md.j2

@@ -86,7 +86,7 @@ Manage specification changes:
 /metaspec.sds.specify       # 2. Define root specification
 /metaspec.sds.plan          # 3. Plan sub-specification architecture
 /metaspec.sds.tasks         # 4. Break down specification tasks
-/metaspec.sds.implement     # 5. Implement sub-specifications
+/metaspec.sds.implement     # 5. Write sub-specification documents (NOT code)
 
 # Quality Assurance (Recommended)
 /metaspec.sds.checklist     # 6. Generate quality checklist