[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CFZK06PWP5S3VQJS7VV34B":3,"skill-same:01M6CFZK06PWP5S3VQJS7VV34B":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M6CFZK06PWP5S3VQJS7VV34B","haiku-start",null,"Start a new H·AI·K·U intent — describe what you want to accomplish and the system creates a structured lifecycle for it","gigsmart\u002Fhaiku-method","gigsmart","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31480897?v=4","01M6CFXPNBQN1BSYBNCKMRS0M6","GigSmart","01M6CFXPSGWGKPZHRZ458SZFVZ",29,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-start\u002FSKILL.md",[],[19,20,21,22,23,24],"start","haiku","haiku start","lifecycle","system","intent","2026-11-10 10:12:30",false,"---\nname: haiku-start\ndescription: Start a new H·AI·K·U intent — describe what you want to accomplish and the system creates a structured lifecycle for it\n---\n\n# Start a New Intent\n\n## Process\n\n**If the user starts the intent with a referenced file** — a spec, a doc, a screenshot, a path like `~\u002FDownloads\u002Fspec.pdf`, or a dragged-in attachment — read it and **synthesize its relevant substance directly into the `description` and `context` you author below.** NEVER store, quote, or reference the file's path in any field. An absolute path leaks the user's machine layout, and the external file won't travel with the intent — the intent must stand on its own from its own text. The path is throwaway; the synthesized content is the durable record. (Read PDFs\u002Fimages natively; capture what they *say*, not where they live.)\n\n1. **Prelaborate** — If the user's description is short (under 2 sentences) or vague, ask 2-3 targeted questions via `AskUserQuestion` to understand scope, desired outcome, and constraints. Fold answers into a richer description (3-5 sentences).\n\n2. **Quick context scan** — Glance at the project structure (2-3 tool calls max) to understand the tech stack and project purpose. This informs studio selection later.\n\n3. **Right-size it — the escape hatch (do this BEFORE creating an intent).** A full multi-stage intent is the right container for a *feature*. It is overkill for a bug fix, a typo, a config tweak, a copy change, or a small localized refactor — work where the whole lifecycle (design → build → review across stages) costs more than the change itself. Assess what the user actually described and pick the lightest container that fits:\n\n   - **Zap-class** — one localized change: a bug fix, a typo, a config\u002Fcopy tweak, a small refactor; touches one or a few files; the cost of a mistake is \"edit and re-run.\" → the right home is **zap**, which writes no intent and no scaffolding.\n   - **Quick-class** — a small but real task that wants one stage's hat loop (plan→do→verify) and a lightweight record, but genuinely does not span multiple stages. → the right home is **quick mode** (a single-stage intent).\n   - **Feature-class** — spans multiple concerns or stages, needs real decomposition \u002F design \u002F cross-stage review, or the user explicitly asked for the full lifecycle. → the full intent below.\n\n   **If it's clearly feature-class, skip straight to step 4 — don't interrupt a real feature with a downgrade prompt.** Otherwise, surface the lighter path with `AskUserQuestion`, recommended option FIRST (so accepting is one tap), and let the user keep the heavier path if they want the tracking:\n\n   - Question: *\"This looks like a `\u003Cbug fix \u002F small task>` — how do you want to run it?\"*\n   - Options, recommended first: **Zap (no intent overhead)** *(when it's zap-class)* \u002F **Quick mode (single stage)** *(when it's quick-class)* \u002F **Full intent (multi-stage lifecycle)**. Offer zap only when it's genuinely zap-class, quick when it's quick-class; always include full as the override.\n\n   **Route on the answer:**\n   - **Zap** → do NOT create an intent. Hand off to the zap flow: call `haiku_zap { task: \"\u003Cthe task, in one or two sentences>\" }` and follow its returned `message` verbatim (see `\u002Fhaiku:haiku-zap`). Stop here — the rest of this skill doesn't apply.\n   - **Quick** → create the intent (step 4), then drive `haiku_run_next` and lock the mode to quick the way `\u002Fhaiku:haiku-quick` does (`haiku_select_mode { options: [\"quick\"] }` after studio selection). The user chose quick here, so locking it honors their choice — you are not dictating the mode.\n   - **Full** (or feature-class) → continue to step 4 unchanged; the user picks the mode via the normal elicitation.\n\n4. **Write the title and description, then create the intent** — You must produce BOTH:\n   - **`title`**: A crisp 3–8 word summary, ≤80 chars, single line, no trailing period. Write it deliberately as a human-readable name for the intent. **Do NOT** pass a truncated description or the first sentence of a paragraph.\n     - Good: `\"Add archivable intents\"`, `\"Migrate auth to OAuth2\"`, `\"Fix mobile nav overflow\"`\n     - Bad: `\"Add archivable intents to H·AI·K·U. Users need a way to soft-hide completed,…\"`\n     - Bad: `\"Implement a new system to allow users to mark intents as\"` (mid-sentence truncation)\n   - **`description`**: The prelaborated narrative (2–5 sentences) covering scope, motivation, and constraints. This is the richer context, not a title.\n   - **`slug`**: Kebab-case identifier (max 40 chars). Usually derived from the title.\n   - **`context`**: Summary of key decisions and constraints from the conversation.\n   - **`studio_candidates`** (**REQUIRED**): The 2–4 studios that best fit what you just described — this pre-narrows the studio picker so the user isn't scrolling the whole registry on every intent. **Call `haiku_studio_list` first** to see the studios with their descriptions, then pick the closest matches (canonical name, slug, or alias all resolve). You have the description in context right now — this is the one moment you can do a semantically-aware pick. The picker shows your shortlist first and keeps the rest behind a \"Show all studios…\" expansion, so narrowing is never lossy — there's no downside to narrowing, so always do it. If you call `haiku_intent_create` without it, the tool rejects the call and tells you to fetch `haiku_studio_list` and retry; don't guess studio names, fetch the list.\n\n   The title and description are distinct fields — the tool does NOT derive one from the other. Writing a lazy title (e.g. the first chunk of the description) will be rejected.\n\n   **Do NOT pass `mode`, `stages`, or `studio`.** Those fields are engine-managed and chosen by the user via the picker. `studio_candidates` is a *hint* that pre-narrows that picker — it does not lock the studio, and the user still makes the final pick. The tool's input schema does not accept `mode`\u002F`stages`\u002F`studio`; trying to pass them will fail validation.\n\n5. **Follow the tool's instructions** — The tool will direct you to call `haiku_run_next`, which then drives the elicitation chain in order:\n   1. `haiku_select_studio` — user picks the studio.\n   2. `haiku_select_mode` — user picks the mode (continuous, discrete, autopilot, quick).\n   3. `haiku_select_stage` — fires only when mode == `quick`, user picks the single stage to run.\n   4. The pre-stage intent review gate opens for the user's approval before any stage starts.\n\n## Notes\n\n- **Never dictate mode or stages.** If the user mentions \"discrete\" or \"single stage\" or \"just inception\" in their description, that's *context for the user when they make the elicit choice* — pass it along into the description if it's load-bearing, but do not pre-set the field. The agent MUST let the user pick via elicitation. (The step-3 escape hatch is not an exception: the user *chooses* the lighter path there, so locking quick afterward honors their pick rather than dictating it.)\n- Do NOT ask the user to pick a studio — the workflow engine handles studio selection via elicitation.\n- If the user already provided a detailed description, skip prelaboration — but still right-size (step 3) before creating the intent.\n- The right-sizing escape hatch is a *recommendation the user confirms*, not a silent reroute: surface it, default to the recommended path, and always leave the full lifecycle available. When in doubt about scope, lean toward offering the lighter option — the user can always decline.\n","# Start a New Intent\n\n## Process\n\n**If the user starts the intent with a referenced file** — a spec, a doc, a screenshot, a path like `~\u002FDownloads\u002Fspec.pdf`, or a dragged-in attachment — read it and **synthesize its relevant substance directly into the `description` and `context` you author below.** NEVER store, quote, or reference the file's path in any field. An absolute path leaks the user's machine layout, and the external file won't travel with the intent — the intent must stand on its own from its own text. The path is throwaway; the synthesized content is the durable record. (Read PDFs\u002Fimages natively; capture what they *say*, not where they live.)\n\n1. **Prelaborate** — If the user's description is short (under 2 sentences) or vague, ask 2-3 targeted questions via `AskUserQuestion` to understand scope, desired outcome, and constraints. Fold answers into a richer description (3-5 sentences).\n\n2. **Quick context scan** — Glance at the project structure (2-3 tool calls max) to understand the tech stack and project purpose. This informs studio selection later.\n\n3. **Right-size it — the escape hatch (do this BEFORE creating an intent).** A full multi-stage intent is the right container for a *feature*. It is overkill for a bug fix, a typo, a config tweak, a copy change, or a small localized refactor — work where the whole lifecycle (design → build → review across stages) costs more than the change itself. Assess what the user actually described and pick the lightest container that fits:\n\n   - **Zap-class** — one localized change: a bug fix, a typo, a config\u002Fcopy tweak, a small refactor; touches one or a few files; the cost of a mistake is \"edit and re-run.\" → the right home is **zap**, which writes no intent and no scaffolding.\n   - **Quick-class** — a small but real task that wants one stage's hat loop (plan→do→verify) and a lightweight record, but genuinely does not span multiple stages. → the right home is **quick mode** (a single-stage intent).\n   - **Feature-class** — spans multiple concerns or stages, needs real decomposition \u002F design \u002F cross-stage review, or the user explicitly asked for the full lifecycle. → the full intent below.\n\n   **If it's clearly feature-class, skip straight to step 4 — don't interrupt a real feature with a downgrade prompt.** Otherwise, surface the lighter path with `AskUserQuestion`, recommended option FIRST (so accepting is one tap), and let the user keep the heavier path if they want the tracking:\n\n   - Question: *\"This looks like a `\u003Cbug fix \u002F small task>` — how do you want to run it?\"*\n   - Options, recommended first: **Zap (no intent overhead)** *(when it's zap-class)* \u002F **Quick mode (single stage)** *(when it's quick-class)* \u002F **Full intent (multi-stage lifecycle)**. Offer zap only when it's genuinely zap-class, quick when it's quick-class; always include full as the override.\n\n   **Route on the answer:**\n   - **Zap** → do NOT create an intent. Hand off to the zap flow: call `haiku_zap { task: \"\u003Cthe task, in one or two sentences>\" }` and follow its returned `message` verbatim (see `\u002Fhaiku:haiku-zap`). Stop here — the rest of this skill doesn't apply.\n   - **Quick** → create the intent (step 4), then drive `haiku_run_next` and lock the mode to quick the way `\u002Fhaiku:haiku-quick` does (`haiku_select_mode { options: [\"quick\"] }` after studio selection). The user chose quick here, so locking it honors their choice — you are not dictating the mode.\n   - **Full** (or feature-class) → continue to step 4 unchanged; the user picks the mode via the normal elicitation.\n\n4. **Write the title and description, then create the intent** — You must produce BOTH:\n   - **`title`**: A crisp 3–8 word summary, ≤80 chars, single line, no trailing period. Write it deliberately as a human-readable name for the intent. **Do NOT** pass a truncated description or the first sentence of a paragraph.\n     - Good: `\"Add archivable intents\"`, `\"Migrate auth to OAuth2\"`, `\"Fix mobile nav overflow\"`\n     - Bad: `\"Add archivable intents to H·AI·K·U. Users need a way to soft-hide completed,…\"`\n     - Bad: `\"Implement a new system to allow users to mark intents as\"` (mid-sentence truncation)\n   - **`description`**: The prelaborated narrative (2–5 sentences) covering scope, motivation, and constraints. This is the richer context, not a title.\n   - **`slug`**: Kebab-case identifier (max 40 chars). Usually derived from the title.\n   - **`context`**: Summary of key decisions and constraints from the conversation.\n   - **`studio_candidates`** (**REQUIRED**): The 2–4 studios that best fit what you just described — this pre-narrows the studio picker so the user isn't scrolling the whole registry on every intent. **Call `haiku_studio_list` first** to see the studios with their descriptions, then pick the closest matches (canonical name, slug, or alias all resolve). You have the description in context right now — this is the one moment you can do a semantically-aware pick. The picker shows your shortlist first and keeps the rest behind a \"Show all studios…\" expansion, so narrowing is never lossy — there's no downside to narrowing, so always do it. If you call `haiku_intent_create` without it, the tool rejects the call and tells you to fetch `haiku_studio_list` and retry; don't guess studio names, fetch the list.\n\n   The title and description are distinct fields — the tool does NOT derive one from the other. Writing a lazy title (e.g. the first chunk of the description) will be rejected.\n\n   **Do NOT pass `mode`, `stages`, or `studio`.** Those fields are engine-managed and chosen by the user via the picker. `studio_candidates` is a *hint* that pre-narrows that picker — it does not lock the studio, and the user still makes the final pick. The tool's input schema does not accept `mode`\u002F`stages`\u002F`studio`; trying to pass them will fail validation.\n\n5. **Follow the tool's instructions** — The tool will direct you to call `haiku_run_next`, which then drives the elicitation chain in order:\n   1. `haiku_select_studio` — user picks the studio.\n   2. `haiku_select_mode` — user picks the mode (continuous, discrete, autopilot, quick).\n   3. `haiku_select_stage` — fires only when mode == `quick`, user picks the single stage to run.\n   4. The pre-stage intent review gate opens for the user's approval before any stage starts.\n\n## Notes\n\n- **Never dictate mode or stages.** If the user mentions \"discrete\" or \"single stage\" or \"just inception\" in their description, that's *context for the user when they make the elicit choice* — pass it along into the description if it's load-bearing, but do not pre-set the field. The agent MUST let the user pick via elicitation. (The step-3 escape hatch is not an exception: the user *chooses* the lighter path there, so locking quick afterward honors their pick rather than dictating it.)\n- Do NOT ask the user to pick a studio — the workflow engine handles studio selection via elicitation.\n- If the user already provided a detailed description, skip prelaboration — but still right-size (step 3) before creating the intent.\n- The right-sizing escape hatch is a *recommendation the user confirms*, not a silent reroute: surface it, default to the recommended path, and always leave the full lifecycle available. When in doubt about scope, lean toward offering the lighter option — the user can always decline.\n",{"name":5,"description":7},"main","42451f546de75e0c4f38d5d3bb0999e54661bf32","plugin\u002Fskills\u002Fhaiku-start",11,"https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method","https:\u002F\u002Fhaikumethod.ai\u002F","https:\u002F\u002Fgithub.com\u002Fgigsmart","https:\u002F\u002Fgigsmart.com","Powering the future of the hourly workforce","2026-05-30 06:22:53",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add gigsmart\u002Fhaiku-method --skill haiku-start",{"tool":46,"command":47},"bunx","bunx skills add gigsmart\u002Fhaiku-method --skill haiku-start",{"tool":49,"command":50},"pnpm","pnpm dlx skills add gigsmart\u002Fhaiku-method --skill haiku-start","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-start\u002FSKILL.md",true,[54,60,64],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fartifacts.md","REFERENCE","参考文档",9058,"https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002Fextensions\u002Fopen-design\u002Fskills\u002Fopen-design\u002Freferences\u002Fartifacts.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fcraft.md",14513,"https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002Fextensions\u002Fopen-design\u002Fskills\u002Fopen-design\u002Freferences\u002Fcraft.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fmotion.md",6573,"https:\u002F\u002Fgithub.com\u002Fcompozy\u002Fcompozy\u002Fblob\u002Fmain\u002Fextensions\u002Fopen-design\u002Fskills\u002Fopen-design\u002Freferences\u002Fmotion.md",[69,83,103,113,125,135],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":25},"01M6CFZZJB7Z2570CM86NW2SQW","haiku-zap","Zero-ceremony single-unit execution — run one task directly through a stage's hat loop without intent or workflow scaffolding","https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-zap\u002FSKILL.md",[],[76,20,77,78,79,80,81,82,24],"zap","haiku zap","workflow","run","ZeRO","execution","loop",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":25},"01M6CFZX5KY8M0279EDA3KB6N7","haiku-version","Show the running H·AI·K·U MCP binary version, plugin version, and whether the engine is the dev source build or the compiled bundle","https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-version\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[95,96,20,97,98,99,100,101,102],"haiku version","version","dev","engine","build","show","plugin","MCP",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":25},"01M6CFZV0TZCWWPKXFW70RSK7N","haiku-unarchive","Unarchive an intent — restore a previously archived intent to default lists","https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-unarchive\u002FSKILL.md",[],[110,20,111,24,112],"haiku unarchive","default","restore",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":25},"01M6CFZS06RDR7ZKDT4AN3B0JP","haiku-triggers","Poll configured providers for events that should create intents or advance gates","https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-triggers\u002FSKILL.md",[],[120,20,121,122,123,124],"haiku triggers","advance","intents","Providers","create",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":25},"01M6CFZQ57PG9X94C504JGZJEY","haiku-studios","Browse available H·AI·K·U studios grouped by category with help links into each studio definition","https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-studios\u002FSKILL.md",[],[132,20,133,134],"haiku studios","browse","help",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":25},"01M6CFZMSWCEHK6NGRAV90D09H","haiku-statusline","Install, remove, or preview the H·AI·K·U custom Claude Code status line — a one-line stage\u002Fphase indicator for the active intent","https:\u002F\u002Fgithub.com\u002Fgigsmart\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-statusline\u002FSKILL.md",[],[142,143,20,144,24,145,146,147,148],"haiku statusline","statusline","status","remove","install","indicator","code"]