[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P922FH3SQZN307YT6RG02M":3,"skill-same:01M6P922FH3SQZN307YT6RG02M":58},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6P922FH3SQZN307YT6RG02M","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","TheBushidoCollective\u002Fhaiku-method","TheBushidoCollective","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F233175215?v=4","01M6P8SCRJW0J2C9YZ0D14R6MA","The Bushido Collective","01M6P8SCX4KGHF4C5GPWEV48SC",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FTheBushidoCollective\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-start\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"start","haiku","haiku start","lifecycle","system","intent","structured","it","you","for","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",0,"https:\u002F\u002Fgithub.com\u002FTheBushidoCollective\u002Fhaiku-method","https:\u002F\u002Fhaikumethod.ai\u002F","https:\u002F\u002Fgithub.com\u002FTheBushidoCollective","https:\u002F\u002Fthebushido.co","Strategic Technology Leadership That Actually Delivers","2026-11-04 00:54:41",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add TheBushidoCollective\u002Fhaiku-method --skill haiku-start",{"tool":50,"command":51},"bunx","bunx skills add TheBushidoCollective\u002Fhaiku-method --skill haiku-start",{"tool":53,"command":54},"pnpm","pnpm dlx skills add TheBushidoCollective\u002Fhaiku-method --skill haiku-start","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheBushidoCollective\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-start\u002FSKILL.md",true,[],[59,78,101,111,126,140],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":29},"01M6P93YBHRPSHMRR5C870HPF8","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\u002FTheBushidoCollective\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-zap\u002FSKILL.md",[],[66,67,20,68,69,70,71,72,73,74,75,76,24,77],"zap","haiku zap","single","unit","stage","scaffolding","task","workflow","run","ZeRO","execution","loop",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":29},"01M6P93D0VA0HWH0NZHER4C6YN","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\u002FTheBushidoCollective\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-version\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[20,90,91,92,93,94,95,96,97,98,99,100],"version","haiku version","show","MCP","plugin","dev","engine","build","binary","bundle","source",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":29},"01M6P93947PNH55ZJ999GZ9J3C","haiku-unarchive","Unarchive an intent — restore a previously archived intent to default lists","https:\u002F\u002Fgithub.com\u002FTheBushidoCollective\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-unarchive\u002FSKILL.md",[],[108,20,24,109,110],"haiku unarchive","restore","default",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":29},"01M6P936W0VF4BE1WR6JGQ6NJW","haiku-triggers","Poll configured providers for events that should create intents or advance gates","https:\u002F\u002Fgithub.com\u002FTheBushidoCollective\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-triggers\u002FSKILL.md",[],[118,119,20,120,121,122,123,124,125,28],"triggers","haiku triggers","events","create","Providers","intents","advance","gates",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":29},"01M6P92V5HDE325PHZHK2BVR7S","haiku-studios","Browse available H·AI·K·U studios grouped by category with help links into each studio definition","https:\u002F\u002Fgithub.com\u002FTheBushidoCollective\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-studios\u002FSKILL.md",[],[20,133,134,135,136,137,138,139],"haiku studios","browse","help","with","links","studio","definition",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":29},"01M6P92KY8511PWQP83YKVFJB3","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\u002FTheBushidoCollective\u002Fhaiku-method\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhaiku-statusline\u002FSKILL.md",[],[20,147,148,149,150,151,152,24,153,154,70,155,28,156,157,158],"statusline","haiku statusline","code","indicator","install","remove","preview","active","line","custom","phase","status"]