From elixir-phoenix
Routes ambiguous work requests to matching /phx: workflows like /phx:investigate for bugs, /phx:plan for features, or /phx:brainstorm for ideation based on keyword signals.
How this skill is triggered — by the user, by Claude, or both
Slash command
/elixir-phoenix:intent-detectionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When user describes work WITHOUT specifying a `/phx:` command, analyze their intent and suggest the appropriate workflow BEFORE starting work.
When user describes work WITHOUT specifying a /phx: command, analyze their intent and suggest the appropriate workflow BEFORE starting work.
| 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 | /phx:compound |
| "enhance plan", "more detail", "deepen" | Plan enhancement | /phx:plan --existing |
| "triage", "which findings", "prioritize fixes" | Finding triage | /phx:triage |
[command] — want me to run it, or should I just dive in?"/phx: command: follow it, don't re-suggestHigh confidence (suggest immediately):
/phx:investigate/phx:plan/phx:reviewMedium confidence (suggest with caveat):
Low confidence (just do it):
When a task matches a workflow command, check complexity before suggesting:
Trivial signals (suggest /phx:quick or handle directly):
Complex signals (suggest /phx:plan or /phx:investigate):
Override rule: If user invokes /phx:full but task matches trivial signals:
"This looks like a quick fix. Want /phx:quick instead, or stick with the full cycle?"
if has_slash_command($ARGUMENTS) -> follow command directly
elif has_stack_trace(message) -> suggest /phx:investigate
elif matches("add|build|implement", message) and multi_step -> suggest /phx:plan
elif matches("fix", message) and small_scope -> handle directly or /phx:quick
elif matches("review|audit", message) -> suggest /phx:review
else -> handle directly (no suggestion)
This skill is consulted at session start. It works alongside:
npx claudepluginhub oliver-kriska/claude-elixir-phoenix --plugin elixir-phoenixRecommends the right /phx: command for planning, review, debug, deploy, or test tasks by classifying user intent from query, git status, and existing plans.
Routes any dropped-in input (idea, spec path, file path, PR/issue, stack trace, bug report) to the correct workflow skill and dispatches it immediately. Acts as the unified entry point before other workflow skills, with optional --safe confirmation gating.