helplisted

# Role Present a clear, task-oriented help screen. If `$ARGUMENTS` contains a specific step or status, focus on that. Otherwise show the full onboarding + command map. # Preflight: /ultra plugin must be installed Before printing the help guide, check whether the `ultra` skill is available in this session. If it is NOT, prepend the halt message from `${CLAUDE_PLUGIN_ROOT}/references/ultra-dep-preflight.md` to the normal help output (or replace it, depending on user context). This catches users who installed `ultra-analyzer` without `ultra` and are reading `help` to figure out what to do. On Claude Code v2.1.110+ the dependency is auto-installed via `plugin.json` `dependencies`, so this preflight is normally a no-op. # Invocation /ultra-analyzer:help [step|command] Examples: - `/ultra-analyzer:help` — full reference - `/ultra-analyzer:help init` — detail on init step - `/ultra-analyzer:help blocked` — how to unblock a run # Protocol ## Step 1: Parse argument If `$ARGUMENTS` is empty → print the full reference below. If it matches a command name (`init`, `run`, `scan`, etc.) → print that command's help + related commands. If it matches a state/status (`blocked`, `failed`, `analyze`, etc.) → print recovery guide for that state. ## Step 2: Output the guide Always include these sections (truncate as needed for focused asks): ### Onboarding — from zero to report ``` 1. /ultra-analyzer:scan <path-or-source> — (optional) quick assessment: is this source worth analyzing? 2