gsd-workflowlisted

# GSD Workflow Routing Route user intent to GSD commands. Explicit /gsd: commands bypass routing -- read `.claude/commands/gsd/[command].md` directly. ## 5-Stage Classification Pipeline When the user provides natural language related to project workflow, route through the GSD Orchestrator's classification pipeline: 1. **Exact match** -- direct command mapping (fastest) 2. **Lifecycle filtering** -- narrow candidates by current project phase 3. **Bayesian classification** -- probabilistic intent matching 4. **Semantic fallback** -- embedding-based similarity for ambiguous requests 5. **Confidence resolution** -- threshold check; ask user if uncertain **When to use the orchestrator:** The user says something like "review the requirements," "what's the project status," "let's verify phase 3," or any natural language that maps to a GSD lifecycle action but doesn't use explicit slash commands. **When to bypass it:** The user types an explicit GSD slash command. Execute directly. **When confidence is low:** Ask the user to clarify rather than guessing. A wrong routing is worse than a clarifying question. ## Quick Command Routing The top-10 most common routes: | User Says | Route To | |-----------|----------| | "what should I work on" | `/gsd:progress` | | "continue where I left off" | `/gsd:progress` | | "build phase X" | `/gsd:execute-phase X` | | "plan the next phase" | `/gsd:plan-phase N` | | "discuss how phase X should work" | `/gsd:discuss-phase N` | | "something's b