docs: fix SDS/SDD command count documentation bug

Fixed incorrect command counts across all documentation:

Core Issue:
- SDS commands: 5 → 8 (was missing: plan, tasks, implement)
- Total commands: 16 → 19 (correct: 8 SDS + 8 SDD + 3 Evolution)

Files Fixed:
1. README.md
   - Quick start example: Added all 8 SDS and 8 SDD commands

2. src/metaspec/templates/base/.metaspec/README.md.j2
   - Header: 16 → 19 commands
   - SDS section: 5 → 8 commands, added plan/tasks/implement
   - Project structure: 16 → 19 commands

3. src/metaspec/templates/base/AGENTS.md.j2
   - For Developers section: 16 → 19 commands with breakdown

4. docs/quickstart.md
   - Command usage comment: 16 → 19 commands

5. docs/architecture.md
   - Template structure: SDS 5 → 8 commands

Impact:
- All generated speckits will now show correct command counts
- Documentation consistency across project
- Bug reported in v0.5.5 resolved

Verification:
✅ File system has 8 SDS + 8 SDD + 3 Evolution = 19 commands
✅ Documentation now matches implementation

Author: NeilJo-GY

README.md

@@ -372,17 +372,25 @@ cd my-spec-kit
 pip install -e .
 
 # Step 4: Use built-in MetaSpec commands for AI-assisted development
-# Phase 1: Define domain specification (SDS)
+# Phase 1: Define domain specification (SDS - 8 commands)
 # /metaspec.sds.constitution  - Define specification design principles
 # /metaspec.sds.specify       - Define specification entities
+# /metaspec.sds.clarify       - Resolve specification ambiguities
 # /metaspec.sds.plan          - Plan specification architecture
+# /metaspec.sds.tasks         - Break down specification work
 # /metaspec.sds.implement     - Write specification documents
+# /metaspec.sds.checklist     - Generate quality checklist
+# /metaspec.sds.analyze       - Check specification consistency
 
-# Phase 2: Develop toolkit (SDD)
+# Phase 2: Develop toolkit (SDD - 8 commands)
 # /metaspec.sdd.constitution  - Define toolkit principles
 # /metaspec.sdd.specify       - Define toolkit specifications
+# /metaspec.sdd.clarify       - Resolve toolkit ambiguities
 # /metaspec.sdd.plan          - Plan implementation architecture
+# /metaspec.sdd.tasks         - Break down implementation work
 # /metaspec.sdd.implement     - Build your speckit
+# /metaspec.sdd.checklist     - Validate quality
+# /metaspec.sdd.analyze       - Check consistency
 
 # Step 5: Share with community
 metaspec contribute my-spec-kit

docs/architecture.md

@@ -41,7 +41,7 @@ src/metaspec/templates/
 │
 └── meta/                     # Third layer: MetaSpec self-development (SDS + SDD)
     ├── sds/                 # Domain specification commands
-    │   └── commands/        # /metaspec.sds.* (5 commands)
+    │   └── commands/        # /metaspec.sds.* (8 commands)
     └── sdd/                 # Speckit development commands
         └── commands/        # /metaspec.sdd.* (8 commands)
 ```

docs/quickstart.md

@@ -103,7 +103,7 @@ cd my-spec-kit
 # Install
 uv pip install -e .
 
-# Use 16 built-in MetaSpec commands (in AI editor)
+# Use 19 built-in MetaSpec commands (in AI editor)
 # SDS: /metaspec.sds.* (8 commands) - Define specification
 # SDD: /metaspec.sdd.* (8 commands) - Develop toolkit
 # Evolution: /metaspec.* (3 commands) - Manage changes

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

@@ -18,15 +18,18 @@ If you just want to **use** {{ name }}, see the root `AGENTS.md` and `README.md`
 
 ## 🏗️ MetaSpec Architecture
 
-This speckit includes 16 AI-assisted development commands organized in three layers:
+This speckit includes 19 AI-assisted development commands organized in three layers:
 
-### Layer 1: SDS (Spec-Driven Specification) - 5 Commands
+### Layer 1: SDS (Spec-Driven Specification) - 8 Commands
 
 Define domain domain specifications:
 
 - `/metaspec.sds.constitution` - Define specification design principles
 - `/metaspec.sds.specify` - Define specification entities, operations, validation rules
 - `/metaspec.sds.clarify` - Resolve ambiguities in domain 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.checklist` - Generate quality checklist for specification
 - `/metaspec.sds.analyze` - Check specification consistency
 
@@ -168,7 +171,7 @@ MetaSpec commands support iteration modes to track progress:
 │   └── {{ package_name }}/
 └── .metaspec/
     ├── README.md          ← You are here
-    ├── commands/          ← 16 MetaSpec commands
+    ├── commands/          ← 19 MetaSpec commands
     └── templates/         ← Output format templates
 ```
 

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

@@ -268,7 +268,7 @@ See `examples/` directory for:
 If you want to **develop or maintain** {{ name }} itself (not just use it), see:
 
 - **`.metaspec/README.md`** - Complete development guide
-- **`.metaspec/commands/`** - 16 AI-assisted MetaSpec commands
+- **`.metaspec/commands/`** - 19 AI-assisted MetaSpec commands (8 SDS + 8 SDD + 3 Evolution)
 
 This includes specifications for defining specifications (SDS), developing toolkit features (SDD), and managing changes (Evolution).