Plugin Help — Interactive Command Advisor
Helps users find the right command, skill, or agent for their situation.
Usage
/skill:phx-help # Analyze context, suggest commands
/skill:phx-help how do I debug this? # Route to /skill:phx-investigate
/skill:phx-help add a new feature # Route to /skill:phx-plan -> /skill:phx-work
Arguments
$ARGUMENTS — optional description of what the user wants to do- Empty = analyze current context (git status, existing plans, file patterns)
Execution Flow
Step 1: Gather Context
If $ARGUMENTS is non-empty, use it as primary signal.
Always gather ambient context (run in parallel):
- Check for existing plans: use Glob on
.claude/plans/*/plan.md — active work in progress?
- Check git status: uncommitted changes? which files?
- Check for solution docs: use Glob on
.claude/solutions/**/*.md — prior knowledge?
Step 2: Classify Intent
Read references/tool-catalog.md for the full routing table.
Map the user's situation to one of these categories:
| Category |
Signals |
Primary Commands |
| Starting out |
No plans, new to plugin |
/skill:phx-intro |
| Ideation |
"explore", "brainstorm", "not sure", "how to approach", "vague idea" |
/skill:phx-brainstorm |
| New feature |
"add", "build", "implement", multi-file |
/skill:phx-plan → /skill:phx-work |
| Quick change |
Single file, <50 lines, "fix typo" |
/skill:phx-quick |
| Bug |
Error, stack trace, "broken", "failing" |
/skill:phx-investigate |
| Review |
"check", "review", PR ready |
/skill:phx-review |
| Performance |
"slow", "N+1", "memory" |
/skill:phx-perf, /skill:ecto-n1-check, /skill:lv-assigns |
| Research |
"how to", "best practice", "evaluate lib" |
/skill:phx-research |
| Resume work |
Existing plan with unchecked tasks |
/skill:phx-work --continue |
| Post-fix |
"that worked", solved a hard bug |
/skill:phx-compound |
| Full cycle |
Large feature, new domain area |
/skill:phx-full |
| Project health |
"audit", "tech debt", "overall quality" |
/skill:phx-audit, /skill:phx-techdebt |
| Dep update audit |
"audit deps", "supply chain", "post-mix deps.update", "review mix.lock PR" |
/skill:phx-deps-audit |
| Manual dep vetting |
"vet this package", "approve dep", "trust ledger", "after /skill:phx-deps-audit findings" |
/skill:phx-deps-vet |
| Deployment |
"deploy", "release", "production" |
/skill:phx-verify then deploy skill |
| Permissions |
"too many prompts", "allow", "permission fatigue" |
/skill:phx-permissions |
| Returning after time off |
"what did I miss", "back from vacation", "catch up", "what changed while I was out" |
/catchup (companion plugin, separate install) |
Step 3: Respond or Clarify
If high confidence (clear match to one category):
Present the recommendation with:
- The command to run (with exact syntax)
- One-line explanation of what it does
- What artifacts it creates (if any)
- Suggested next step after it completes
If medium confidence (2-3 possible matches):
Use AskUserQuestion with the top options, each with a one-line explanation.
If low confidence (vague or no signal):
Ask ONE focused clarifying question. Examples:
- "Are you starting something new or continuing existing work?"
- "Is this a bug fix or a new feature?"
- "How many files do you expect to change?"
Then recommend based on the answer.
Step 4: Offer Follow-up
After recommending, always add:
- "Run
/skill:phx-help anytime to get routing advice"
- If they seem new: "Try
/skill:phx-intro for a full plugin walkthrough"
Iron Laws
- ONE recommendation — don't dump the full catalog, pick the best match
- MAX ONE clarifying question — don't interrogate, make your best guess
- Show exact syntax —
/skill:phx-plan Add user notifications not just "use the plan command"
- Context over keywords — existing plans + git state matter more than word matching
- NEVER block — if user already knows what they want, DO NOT redirect
Integration
- Complements
intent-detection (auto-trigger) with explicit invocation
- References same routing logic but adds interactive clarification
- Can recommend
/skill:phx-intro for onboarding
1---2name: phx-help3description: Choose Phoenix review, plan, debug, or test command. Use when user asks which /skill:phx-* command or plugin skill handles a task; do not route only to a domain skill. NEVER for bare /help; NOT for ambiguous requests (use intent-detection) or a plugin tour.4---56# Plugin Help — Interactive Command Advisor78Helps users find the right command, skill, or agent for their situation.910## Usage1112```13/skill:phx-help # Analyze context, suggest commands14/skill:phx-help how do I debug this? # Route to /skill:phx-investigate15/skill:phx-help add a new feature # Route to /skill:phx-plan -> /skill:phx-work16```1718## Arguments1920- `$ARGUMENTS` — optional description of what the user wants to do21- Empty = analyze current context (git status, existing plans, file patterns)2223## Execution Flow2425### Step 1: Gather Context2627If `$ARGUMENTS` is non-empty, use it as primary signal.2829Always gather ambient context (run in parallel):30311. Check for existing plans: use Glob on `.claude/plans/*/plan.md` — active work in progress?322. Check git status: uncommitted changes? which files?333. Check for solution docs: use Glob on `.claude/solutions/**/*.md` — prior knowledge?3435### Step 2: Classify Intent3637Read `references/tool-catalog.md` for the full routing table.3839Map the user's situation to one of these categories:4041| Category | Signals | Primary Commands |42|----------|---------|-----------------|43| **Starting out** | No plans, new to plugin | `/skill:phx-intro` |44| **Ideation** | "explore", "brainstorm", "not sure", "how to approach", "vague idea" | `/skill:phx-brainstorm` |45| **New feature** | "add", "build", "implement", multi-file | `/skill:phx-plan` → `/skill:phx-work` |46| **Quick change** | Single file, <50 lines, "fix typo" | `/skill:phx-quick` |47| **Bug** | Error, stack trace, "broken", "failing" | `/skill:phx-investigate` |48| **Review** | "check", "review", PR ready | `/skill:phx-review` |49| **Performance** | "slow", "N+1", "memory" | `/skill:phx-perf`, `/skill:ecto-n1-check`, `/skill:lv-assigns` |50| **Research** | "how to", "best practice", "evaluate lib" | `/skill:phx-research` |51| **Resume work** | Existing plan with unchecked tasks | `/skill:phx-work --continue` |52| **Post-fix** | "that worked", solved a hard bug | `/skill:phx-compound` |53| **Full cycle** | Large feature, new domain area | `/skill:phx-full` |54| **Project health** | "audit", "tech debt", "overall quality" | `/skill:phx-audit`, `/skill:phx-techdebt` |55| **Dep update audit** | "audit deps", "supply chain", "post-`mix deps.update`", "review mix.lock PR" | `/skill:phx-deps-audit` |56| **Manual dep vetting** | "vet this package", "approve dep", "trust ledger", "after /skill:phx-deps-audit findings" | `/skill:phx-deps-vet` |57| **Deployment** | "deploy", "release", "production" | `/skill:phx-verify` then deploy skill |58| **Permissions** | "too many prompts", "allow", "permission fatigue" | `/skill:phx-permissions` |59| **Returning after time off** | "what did I miss", "back from vacation", "catch up", "what changed while I was out" | `/catchup` (companion plugin, separate install) |6061### Step 3: Respond or Clarify6263**If high confidence** (clear match to one category):64Present the recommendation with:6566- The command to run (with exact syntax)67- One-line explanation of what it does68- What artifacts it creates (if any)69- Suggested next step after it completes7071**If medium confidence** (2-3 possible matches):72Use `AskUserQuestion` with the top options, each with a one-line explanation.7374**If low confidence** (vague or no signal):75Ask ONE focused clarifying question. Examples:7677- "Are you starting something new or continuing existing work?"78- "Is this a bug fix or a new feature?"79- "How many files do you expect to change?"8081Then recommend based on the answer.8283### Step 4: Offer Follow-up8485After recommending, always add:8687- "Run `/skill:phx-help` anytime to get routing advice"88- If they seem new: "Try `/skill:phx-intro` for a full plugin walkthrough"8990## Iron Laws91921. **ONE recommendation** — don't dump the full catalog, pick the best match932. **MAX ONE clarifying question** — don't interrogate, make your best guess943. **Show exact syntax** — `/skill:phx-plan Add user notifications` not just "use the plan command"954. **Context over keywords** — existing plans + git state matter more than word matching965. **NEVER block** — if user already knows what they want, DO NOT redirect9798## Integration99100- Complements `intent-detection` (auto-trigger) with explicit invocation101- References same routing logic but adds interactive clarification102- Can recommend `/skill:phx-intro` for onboarding
oliver-kriska