Menu
Install, remove, or preview the H·AI·K·U custom Claude Code status line — a one-line stage/phase indicator for the active intent
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Quick mode for small tasks — single-stage intent with auto-advance
Start a new H·AI·K·U intent — describe what you want to accomplish and the system creates a structured lifecycle for it
Full autonomous workflow — elaborate, plan, build, review, and deliver in one command
Open the SPA review pane for an intent so the user can browse units, feedback, stage artifacts, and outputs. Non-blocking on the workflow — leaves feedback that the engine picks up on the next tick. Use whenever the user wants to "see," "open," "show," or "look at" the current intent or a specific stage.
Reverse-engineer an existing feature into H·AI·K·U intent artifacts
Zero-ceremony single-unit execution — run one task directly through a stage's hat loop without intent or workflow scaffolding
| name | haiku-statusline |
| description | Install, remove, or preview the H·AI·K·U custom Claude Code status line — a one-line stage/phase indicator for the active intent |
H·AI·K·U ships a custom Claude Code status line that shows, at a glance, where the active intent is in its lifecycle:
⬢ admin-portal-reimagine · ⬢⬢⬢⬣⬡⬡ development ❯ execute · 7/12 units
⬢ brand mark · then the intent slug⬢ complete · ⬣ active (phase-hued) · ⬡ pending❯ running · ⊘ gated), and the phase (color-coded: execute=cyan, fix-loop=orange, review/approve=yellow, gate=magenta, elaborate=grey)When you're not on an active intent (no .haiku/, the intent is sealed, or you're outside a project), it transparently falls back to whatever status line you had before — it's purely additive.
Run the install command from the project (or pass --global to wire ~/.claude/settings.json):
haiku statusline install
This points Claude Code's statusLine at haiku statusline and saves your existing status line as the fallback (in .haiku/statusline-fallback.json, or ~/.haiku/ for --global). The status line refreshes on the next prompt.
.claude/settings.json.--global: wires the user-level ~/.claude/settings.json so the haiku line shows in every project (and falls back to your original line outside intents).haiku statusline uninstall
Restores the original status line you had before install (or removes the statusLine key entirely if you had none). Add --global if you installed globally.
To see the line for the current project without installing, feed the status-line payload to the render command:
echo "{\"workspace\":{\"current_dir\":\"$PWD\"}}" | haiku statusline
Set NO_COLOR=1 for a plain (no-ANSI) line; set HAIKU_STATUSLINE_DEBUG=1 to print on stderr why it rendered nothing (no .haiku/, sealed intent, etc.).
HAIKU_STATUSLINE_DEBUG=1 to see the reason.statusLine key; every other setting in .claude/settings.json is preserved..claude/settings.local.json → project .claude/settings.json → ~/.claude/settings.json) and, at whichever file haiku installed itself into, substituting the original line saved at install. So a status line you keep in a settings file haiku never touched (e.g. a project line when haiku is installed globally) still wins — the saved fallback record is only the last resort.npx -y @haiku/haiku statusline so it survives plugin updates with no path to rot; a dev checkout writes the absolute path to the bin dispatcher (npx can't resolve an unpublished local package). Claude Code runs the status-line command without the plugin bin on PATH, so neither form relies on PATH.