intent-detection

# Intent Detection — Workflow Routing When user describes work WITHOUT specifying a `/phx:` command, analyze their intent and suggest the appropriate workflow BEFORE starting work. ## Routing Table | Signal | Detected Intent | Suggest | |--------|----------------|---------| | "bug", "error", "crash", "failing", "broken", stack trace | Bug investigation | `/phx:investigate` | | "brainstorm", "explore idea", "not sure what I need", "vague idea", "let's discuss", "how to approach" | Ideation/requirements | `/phx:brainstorm` | | "add", "implement", "build", "create" + multi-step | New feature | `/phx:plan` | | "review", "check", "audit" code | Code review | `/phx:review` | | "fix" + small/specific scope | Quick fix | handle directly or `/phx:quick` | | "refactor", "clean up", "improve" | Refactoring | `/phx:plan` (needs scope) | | "research", "how to", "what's the best" | Research | `/phx:research` | | "evaluate", "compare", "adopt", "library", "should we use" | Library evaluation | `/phx:research --library` | | "test", "spec", "coverage" | Testing | handle directly or `/phx:plan` | | Describes 1-2 file changes, < 50 lines | Small task | handle directly | | "deploy", "release", "production" | Deployment | `/phx:verify` then deploy | | "performance", "slow", "N+1", "memory" | Performance | `/phx:perf` | | "PR review", "review comments", "address feedback", "respond to PR" | PR response | `/phx:pr-review` | | "that worked", "fixed it", "problem solved" | Knowledge capture | `/ph...