refactor: standardize workflow descriptions for skill generation

Update all 21 workflow descriptions to follow consistent format:
- Short human-readable prefix
- Explicit trigger phrases with intent markers
- Max 2 phrases per workflow to reduce false positives
- Avoid substring matching issues with questions

This improves workflow routing accuracy for AI skill invocation.

Author: bmadcode

src/workflows/1-preproduction/brainstorm-game/workflow.yaml

@@ -1,6 +1,6 @@
 # Brainstorm Game Workflow Configuration
 name: "brainstorm-game"
-description: "Facilitate game brainstorming sessions with game-specific context, guidance, and game design techniques."
+description: "Game concept ideation with guided design techniques. Use when the user says 'lets create game design ideas' or 'I want to brainstorm game concepts'"
 author: "BMad"
 
 # Critical variables from config

src/workflows/1-preproduction/game-brief/workflow.yaml

@@ -1,6 +1,6 @@
 # Game Brief - Interactive Workflow Configuration
 name: game-brief
-description: "Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration"
+description: "Game vision definition workflow. Use when the user says 'lets create a game brief' or 'I want to define my game vision'"
 author: "BMad"
 
 # Critical variables from config

src/workflows/2-design/gdd/workflow.yaml

@@ -1,6 +1,6 @@
 # Game Design Document (GDD) Workflow
 name: gdd
-description: "Game Design Document workflow for all game project levels - from small prototypes to full AAA games. Generates comprehensive GDD with game mechanics, systems, progression, and implementation guidance."
+description: "Comprehensive game design document creator. Use when the user says 'lets create a game design document' or 'I want to create a comprehensive GDD'"
 author: "BMad"
 
 # Critical variables from config

src/workflows/2-design/narrative/workflow.yaml

@@ -1,6 +1,6 @@
 # Narrative Design Workflow
 name: narrative
-description: "Narrative design workflow for story-driven games. Creates comprehensive narrative documentation including story structure, character arcs, world-building, dialogue systems, and production planning."
+description: "Story-driven narrative design documentation. Use when the user says 'lets create a narrative design document'"
 author: "BMad"
 
 # Critical variables from config

src/workflows/3-technical/game-architecture/workflow.yaml

@@ -1,6 +1,6 @@
 # Game Architecture Workflow Configuration
 name: game-architecture
-description: "Collaborative game architecture workflow for AI-agent consistency. Intelligent, adaptive conversation that produces a decision-focused game architecture document covering engine, systems, networking, and technical design optimized for game development."
+description: "Technical game systems architecture design. Use when the user says 'lets create a game architecture' or 'I want to design technical game systems'"
 author: "BMad"
 
 # Critical variables

src/workflows/3-technical/generate-project-context/workflow.md

@@ -1,6 +1,6 @@
 ---
 name: generate-project-context
-description: Creates a concise project-context.md file with critical rules and patterns that AI agents must follow when implementing game code. Optimized for LLM context efficiency.
+description: Generate AI-optimized project context file. Use when the user says 'lets create project context for game dev'
 ---
 
 # Generate Project Context Workflow

src/workflows/4-production/code-review/workflow.yaml

@@ -1,6 +1,6 @@
 # Review Story Workflow - Game Development
 name: code-review
-description: "Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval. Game-specific focus on 60fps, feel, and platform considerations."
+description: "Adversarial game dev code review. Use when the user says 'lets review this code for game dev issues'"
 author: "BMad"
 
 # Critical variables from config

src/workflows/4-production/correct-course/workflow.yaml

@@ -1,6 +1,6 @@
 # Correct Course - Sprint Change Management Workflow
 name: "correct-course"
-description: "Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation"
+description: "Sprint change impact analysis and planning. Use when the user says 'I want to analyze and plan significant sprint changes'"
 author: "BMad Method"
 
 config_source: "{project-root}/_bmad/gds/config.yaml"

src/workflows/4-production/create-story/workflow.yaml

@@ -1,5 +1,5 @@
 name: create-story
-description: "Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking"
+description: "User story creation from epics. Use when the user says 'lets create a user story' or 'I want to create a user story'"
 author: "BMad"
 
 # Critical variables from config

src/workflows/4-production/dev-story/workflow.yaml

@@ -1,5 +1,5 @@
 name: dev-story
-description: "Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria"
+description: "Story implementation and testing workflow. Use when the user says 'lets implement story tasks' or 'lets write tests for story'"
 author: "BMad"
 
 # Critical variables from config