Menü
Full autonomous workflow — elaborate, plan, build, review, and deliver in one command
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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
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-autopilot |
| description | Full autonomous workflow — elaborate, plan, build, review, and deliver in one command |
Run the full H·AI·K·U lifecycle autonomously from description to delivery. Autopilot is one of the three intent modes (discrete | continuous | autopilot). It tells the workflow engine to promote ask review gates to auto, so the lifecycle advances without human intervention on stage gates. External gates and the intent-completion review still pause (structural signals the workflow engine can't synthesize).
/haiku:haiku-start, then set autopilot with haiku_select_mode { intent: "<slug>", modes: ["autopilot"] }. Passing a single mode auto-selects it (no picker pause) and writes mode: autopilot plus the studio's full stage list. Do NOT pass mode to haiku_intent_create — studio/mode/stage are engine-managed and start unset.haiku_select_mode { intent: "<slug>", modes: ["autopilot"] } — a single-option list auto-selects with no picker pause and writes mode (+ stages) through the one engine-sanctioned path. Do NOT use haiku_intent_set { field: "mode" } or haiku_human_write — mode is an engine-managed field that both reject (intent_field_engine_only); haiku_select_mode is the ONLY mode setter. Do NOT set a separate autopilot: true boolean — that is a deprecated pattern. (If the intent has already started a stage, select_mode refuses transitions into/out of quick; surface that to the user.)haiku_intent_set { intent: "<slug>", field: "intent_completion_review", value: false }. Do NOT set this unless the user explicitly wants truly headless completion; the completion review is the bookend that prevents silent intent-completion on stage-gate pass.haiku_run_next { intent: "<slug>" }. Repeat on every return. When a subagent returns, re-call haiku_run_next to advance.external or compound [external, ask]). They need a real PR/MR merge signal and cannot be auto-approved.await gates. Waiting for a non-review external event (customer response, pipeline, etc.).intent_completion_review: false is set on the intent).haiku_run_next returns external_review_requested mid-lifecycle (e.g. per-unit MRs in discrete mode), surface the PR creation step to the user — don't open PRs autonomously. The final intent-completion delivery PR is the exception: after intent_complete, open the delivery PR (haiku/<slug>/main → main) directly. The intent-completion review gate is the human checkpoint; pausing again is redundant.error, max_bolts_exceeded, unit_scope_violation not clearable after one retry, or any workflow engine rejection that persists across two calls → stop and report./haiku:haiku-quick + autopilot: set stages: [<one>] AND mode: autopilot. Single-stage, no pauses except external/completion gates.