بنقرة واحدة
haiku-adopt
Reverse-engineer an existing feature into H·AI·K·U intent artifacts
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Reverse-engineer an existing feature into H·AI·K·U intent artifacts
التثبيت باستخدام 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.
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-adopt |
| description | Reverse-engineer an existing feature into H·AI·K·U intent artifacts |
Reverse-engineer an existing feature into H·AI·K·U intent artifacts.
CRITICAL: MUST NOT modify existing code. Adopted units describe what already exists — they are written with synthetic terminal iterations[] (last entry result: "advance") and signed reviews{} / approvals{} so the cursor sees them as completed and never dispatches a hat against them. Forward-only invariant: completed work is immutable.
Wait for user confirmation at each gate (Phase 3, 4, 5).