phxhelp

# Plugin Help — Interactive Command Advisor Helps users find the right command, skill, or agent for their situation. ## Usage ``` /phx:help # Analyze context, suggest commands /phx:help how do I debug this? # Route to /phx:investigate /phx:help add a new feature # Route to /phx:plan -> /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): 1. Check for existing plans: use Glob on `.claude/plans/*/plan.md` — active work in progress? 2. Check git status: uncommitted changes? which files? 3. 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 | `/phx:intro` | | **Ideation** | "explore", "brainstorm", "not sure", "how to approach", "vague idea" | `/phx:brainstorm` | | **New feature** | "add", "build", "implement", multi-file | `/phx:plan` → `/phx:work` | | **Quick change** | Single file, <50 lines, "fix typo" | `/phx:quick` | | **Bug** | Error, stack trace, "broken", "fai...