when-creating-slash-commands-use-slash-command-encoder

# Slash Command Encoder SOP ## Overview Create ergonomic slash commands (/command) for fast, unambiguous access to micro-skills with auto-discovery, intelligent routing, parameter validation, and command chaining. ## Agents & Responsibilities ### coder **Role:** Command implementation and handler logic **Responsibilities:** - Implement command handlers - Create validation logic - Build routing mechanisms - Test command functionality ### base-template-generator **Role:** Generate command templates and boilerplate **Responsibilities:** - Create command templates - Generate documentation - Build example commands - Create test scaffolding ## Phase 1: Design Command Interface ### Objective Design command syntax, parameters, and behavior specifications. ### Scripts ```bash # Generate command template npx claude-flow@alpha command template \ --name "analyze" \ --description "Analyze codebase for patterns" \ --output commands/analyze.js # Define command schema cat > command-schema.json <<EOF { "name": "analyze", "alias": "a", "description": "Analyze codebase for patterns", "parameters": [ { "name": "path", "type": "string", "required": true, "description": "Path to analyze" }, { "name": "depth", "type": "number", "required": false, "default": 3, "description": "Analysis depth" } ], "examples": [ "/analyze ./src", "/analyze ./src --depth 5" ] } EOF # Validate schema npx claude-...