Menu
Quick mode for small tasks — single-stage intent with auto-advance
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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
Admin tools for unsticking corrupt intents — force a stage complete, set intent fields, reset drift, mutate feedback. Every mutation requires user confirmation via the SPA picker.
| name | haiku-quick |
| description | Quick mode for small tasks — single-stage intent with auto-advance |
A quick task is a regular intent in quick mode (single-stage). The workflow engine's elicitation chain handles studio + stage selection; the only difference vs /haiku:haiku-start is that mode is locked to quick (skipping the mode-elicit step).
AskUserQuestion with options[]. Otherwise skip.haiku_intent_create:
title: 3–8 words, ≤80 chars, single line. NOT a truncated description. Good: "Fix login button padding". Bad: "Fix login button padding on mobile because…"description: 2–5 sentences of context.studio_candidates (REQUIRED): the 2–4 studios that best fit, from haiku_studio_list. Fetch the list, pick the closest matches, pass their canonical names. The tool rejects the call without it (and tells you to fetch the list and retry).mode or stages — engine-managed. The tool will reject them.haiku_run_next { intent: "<slug>" }. The workflow engine routes to select_studio first; the agent calls haiku_select_studio.select_mode. Call haiku_select_mode { intent: "<slug>", options: ["quick"] } — passing options: ["quick"] locks the mode without showing the picker (this is the only thing that distinguishes /haiku:haiku-quick from /haiku:haiku-start).select_stage. Call haiku_select_stage { intent: "<slug>" } — this elicits a single stage from the studio's stage list.haiku_run_next advances through the pre-stage intent review and into the chosen stage./haiku:haiku-start instead — don't cram it into a single stage.mode or stages directly to haiku_intent_create. Both are engine-controlled.haiku_select_stage's elicit — the agent does not pre-fill it unless the user already explicitly chose one in conversation, in which case pass options: ["<chosen-stage>"].