intent-detection

name	intent-detection
description	Use when planning Ruby/Rails task without slash command: route to /rb: command. Does NOT handle: known slash command.
when_to_use	Triggers: what command, which rb, suggest command.
user-invocable	false
effort	low

Intent Detection — Workflow Routing

When user describes work WITHOUT specifying a /rb: 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	/rb:investigate
"add", "implement", "build", "create" + multi-step	New feature	/rb:plan
"review", "check", "audit" code	Code review	/rb:review
"fix" + small/specific scope	Quick fix	handle directly or /rb:quick
"refactor", "clean up", "improve"	Refactoring	/rb:plan (needs scope)
"research", "how to", "what's the best"	Research	/rb:research
"evaluate", "compare", "adopt", "library", "should we use"	Library evaluation	/rb:research --library
"test", "spec", "coverage"	Testing	handle directly or /rb:plan
Describes 1-2 file changes, < 50 lines	Small task	handle directly
"deploy", "release", "production"	Deployment	/rb:verify then deploy
"performance", "slow", "N+1", "memory"	Performance	/rb:perf
"PR review", "review comments", "address feedback", "respond to PR"	PR response	/rb:pr-review
"permission prompts", "stop asking", "settings.json", "allow commands", "permission fatigue"	Permission tuning	/rb:permissions
"that worked", "fixed it", "problem solved"	Knowledge capture	/rb:compound
"enhance plan", "more detail", "deepen"	Plan enhancement	/rb:plan --existing
"triage", "which findings", "prioritize fixes"	Finding triage	/rb:triage
"brainstorm", "explore options", "not sure how", "multiple approaches", "what's the best way to architect"	Design exploration	/rb:brainstorm

Behavior

1. Read user's first message
2. Match against routing table (use keyword + context signals, not exact match)
3. If lock (single valid route): suggest the command directly — "This looks like [intent]. I'd suggest [command] — want me to run it, or should I just dive in?"
4. If fork (multiple valid routes): present top 2-3 options with one-sentence rationale each
5. If trivial task (typo, single-line fix, config change): skip suggestion, just do it
6. If user already specified a /rb: command: follow it, don't re-suggest
7. NEVER block the user — suggestion only, not mandatory

Routing Modes

Lock (single valid route — act immediately)

High confidence, one right answer. Don't deliberate — suggest directly:

• Stack trace or error message pasted → /rb:investigate
• "Fix CI" / "fix rubocop" → auto-fix pattern
• "Run checks" → /rb:verify
• "Permission prompts annoying" → /rb:permissions
• "That fixed it" → /rb:compound
• "Add [feature] with [multiple components]" → /rb:plan
• "Review my changes" or "check this PR" → /rb:review

Fork (multiple valid routes — don't pick silently)

Genuinely ambiguous. Present top 2-3 options with one-sentence rationale each:

• "Work on billing feature" → /rb:plan or /rb:work depending on whether plan exists
• "Improve the auth flow" → /rb:plan (scope unclear) or /rb:investigate (if bugs mentioned)
• "Clean up this module" → /rb:quick (small) or /rb:plan (large) — ask about scope
• "Fix [thing]" — could be quick or complex, suggest based on scope description
• "Update [thing]" — could be small edit or refactor

Trivial (just do it)

Low confidence or obvious scope. Don't suggest a workflow:

• Single file mentioned, clear change
• "Change X to Y"
• Configuration or dependency updates

Complexity Signals

When a task matches a workflow command, check complexity before suggesting:

Trivial signals (suggest /rb:quick or handle directly):

• Single file mentioned explicitly
• "exclude X from Y", "add X to config", "rename", "change X to Y"
• Problem + solution both stated ("X is wrong, change to Y")
• One-line fix described

Complex signals (suggest /rb:plan or /rb:investigate):

• 3+ modules or files mentioned
• "intermittent", "race condition", "sometimes", "random"
• Stack trace with 5+ frames
• "across", "all", "every" (scope indicators)

Override rule: If user invokes /rb:full but task matches trivial signals: "This looks like a quick fix. Want /rb:quick instead, or stick with the full cycle?"

Iron Laws

1. NEVER block on suggestion — If user starts explaining, just do the work
2. One suggestion max — Don't re-suggest if user ignores first suggestion
3. Commands are shortcuts, not gates — All work can be done without commands

Integration

This skill is consulted at session start. It works alongside:

• SessionStart hook (shows plugin loaded message + injects Iron Laws + Preferences)
• Individual workflow skills (activated by commands)