fix: add missing 4 SDS commands to generator

Bug: generator.py only registered 4 SDS commands, but we have 8 template files

Fixed:
- Added missing commands to sds_commands list:
  - plan (plan protocol architecture)
  - tasks (break down specification work)
  - implement (write spec documents)
  - checklist (quality checklist)
- Updated comment: 4 commands → 8 commands
- Updated meta/README.md command list

Now metaspec init will generate all 19 commands:
- 8 SDS commands ✅
- 8 SDD commands ✅
- 3 Evolution commands ✅

Files changed:
- src/metaspec/generator.py
- src/metaspec/templates/meta/README.md

Author: NeilJo-GY

src/metaspec/generator.py

@@ -274,16 +274,20 @@ def _select_templates(self, meta_spec: MetaSpecDefinition) -> dict[str, str]:
         # 3. MetaSpec commands and templates for speckit development → .metaspec/
         # These provide AI-assisted workflow for developing the speckit itself
         # Three-layer architecture:
-        #   - SDS (Spec-Driven Specification): 4 commands for protocol definition
+        #   - SDS (Spec-Driven Specification): 8 commands for protocol definition
         #   - SDD (Spec-Driven Development): 8 commands for toolkit development
         #   - Evolution: 3 shared commands for specification evolution
 
-        # SDS commands (4): Protocol specification definition
+        # SDS commands (8): Protocol specification definition
         # File naming: metaspec.sds.{command}.md to use /metaspec.sds.{command} prefix
         sds_commands = [
             "constitution",  # Define protocol principles
-            "specify",  # Define protocol entities
+            "specify",  # Define protocol entities and operations
             "clarify",  # Resolve protocol ambiguities
+            "plan",  # Plan protocol architecture and sub-specifications
+            "tasks",  # Break down protocol specification work
+            "implement",  # Write protocol specification documents
+            "checklist",  # Generate quality checklist for protocol
             "analyze",  # Check protocol consistency
         ]
 

src/metaspec/templates/meta/README.md

@@ -29,7 +29,7 @@ meta/ adopts a clear three-layer architecture, separating commands at different
 
 ```
 meta/
-├── sds/              # Spec-Driven Specification (5 commands)
+├── sds/              # Spec-Driven Specification (8 commands)
 │   ├── commands/     # Protocol specification definition commands
 │   └── templates/    # (Current commands reference protocol templates under shared templates/)
 │
@@ -120,7 +120,7 @@ See: `/metaspec.sdd.specify`, `/metaspec.sdd.plan`, `/metaspec.sdd.implement`
 
 ## Command List
 
-### SDS Commands (4) - Protocol Specification
+### SDS Commands (8) - Protocol Specification
 
 Generated command prefix: `/metaspec.sds.*`
 
@@ -129,10 +129,15 @@ Generated command prefix: `/metaspec.sds.*`
 | `constitution` | Define protocol design principles | memory/constitution.md |
 | `specify` | Define protocol entities and rules | specs/protocol/00X-name/spec.md |
 | `clarify` | Resolve protocol ambiguities | Update spec.md |
+| `plan` | Plan protocol architecture and sub-specifications | specs/protocol/00X-name/plan.md |
+| `tasks` | Break down protocol specification work | specs/protocol/00X-name/tasks.md |
+| `implement` | Write protocol specification documents | Create/update spec files |
+| `checklist` | Generate quality checklist for protocol | specs/protocol/00X-name/checklists/ |
 | `analyze` | Check protocol consistency | Analysis report |
 
 **Use Cases**:
 - Define domain protocols (e.g., MCP, GraphQL)
+- Plan and implement complex protocol hierarchies
 - Define validation rules and constraints
 - Implementation-independent specifications