一键导入
haiku-zap
Zero-ceremony single-unit execution — run one task directly through a stage's hat loop without intent or workflow scaffolding
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Zero-ceremony single-unit execution — run one task directly through a stage's hat loop without intent or workflow scaffolding
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 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
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-zap |
| description | Zero-ceremony single-unit execution — run one task directly through a stage's hat loop without intent or workflow scaffolding |
Run a single task directly through a stage's hat loop — no intent file, no unit decomposition, no workflow tick. Stateless: nothing is written to .haiku/. Use it for bug fixes, typos, config tweaks, and small refactors where the cost of a mistake is "edit and re-run."
Call haiku_zap { task: "<the task>", studio?, stage? }.
studio / stage are optional. Omit them to default to the build-class execution stage of the software studio.zap_studio_not_found or zap_stage_not_found, surface the valid_studios / valid_stages list with AskUserQuestion, let the user pick, and call haiku_zap again with their choice.message verbatim. It contains the resolved studio/stage, the ordered hat sequence with each hat's role, a ready-to-spawn subagent prompt per hat, and the full run/verify/commit procedure (preflight, sequential dispatch, PASS/FAIL parsing, retry cap, commit-only-on-PASS).