[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M781S0RF2MT5BYK4T52X1MMD":3,"skill-same:01M781S0RF2MT5BYK4T52X1MMD":46},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M781S0RF2MT5BYK4T52X1MMD","spec-kitty.research",null,"Capture discovery findings before specification","spec-kitty\u002Fspec-kitty-open-packs","spec-kitty","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F299193673?v=4","01M781PAHK4SK9KA0V4KT7R3XN","Spec Kitty","01M781PAJDDBGZA6R83VQKWW90",2,"MIT","https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec-kitty.research\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: spec-kitty.research\ndescription: Capture discovery findings before specification\nuser-invocable: true\n---\n## Startup Upgrade Check\n\nRun this at most once per active agent session before the first Spec Kitty command workflow.\nIf you already ran `spec-kitty upgrade --agent-check --json` in this session, reuse that result and skip this block.\nDo not run or announce an upgrade check again for later Spec Kitty commands in the same session.\nOtherwise, before continuing, run:\n\n```bash\nspec-kitty upgrade --agent-check --json\n```\n\nIf JSON `action` is `none`, continue.\nIf `action` is `auto_upgrade`, run `upgrade_command` before continuing. If it fails, tell the user and continue with the current Spec Kitty version.\nIf `action` is `guidance`, show `upgrade_note` briefly, then continue.\nIf `action` is `prompt`, ask the user with the host-native question UI when available:\n\n`Spec Kitty {latest_version} is available. You are on {installed_version}. Upgrade now?`\n\nUse these choices:\n\n1. Upgrade now (recommended) - record `upgrade_now`, run `upgrade_command`, then continue.\n2. Always keep me up to date - record `always`, run `upgrade_command`, then continue.\n3. Not now - record `not_now`, then continue.\n4. Never ask again - record `never_ask`, then continue.\n\nRecord the selected choice before continuing:\n\n```bash\nspec-kitty upgrade --agent-choice \u003Cupgrade_now|always|not_now|never_ask> --agent-latest \u003Clatest_version> --json\n```\n\nIf no host-native question UI is available, present the same four choices in plain text and wait for the user.\nIn non-interactive hosts, choose `not_now` and continue.\n\n\n**Path reference rule:** When you mention directories or files, provide either the absolute path or a path relative to the project root (for example, `\u003Cmission_dir>\u002Ftasks\u002F`). Never refer to a folder by name alone.\n\n**In repos with multiple missions, always pass `--mission \u003Chandle>` to every spec-kitty command.** The `\u003Chandle>` can be the mission's `mission_id` (ULID), `mid8` (first 8 chars of the ULID), or `mission_slug`. The resolver disambiguates by `mission_id` and returns a structured `MISSION_AMBIGUOUS_SELECTOR` error on ambiguity — there is no silent fallback.\n\n## User Input\n\nThe content of the user's message that invoked this skill (everything after the skill invocation token, e.g. after `\u002Fspec-kitty.\u003Ccommand>` or `$spec-kitty.\u003Ccommand>`) is the User Input referenced elsewhere in these instructions.\n\nYou **MUST** consider this user input before proceeding (if not empty).\n\n## Goal\n\nThis is the mission's `discovery` step (not the `\u002Fspec-kitty.specify`\ndiscovery interview). Capture discovery findings — the facts, decisions, and\nopen questions gathered before a spec exists — so `\u002Fspec-kitty.specify` and\n`\u002Fspec-kitty.plan` can build on them instead of rediscovering the same\nground.\n\n## Location\n\nThis step runs before a spec or plan exists, on whatever branch your mission's\nplanning artifacts land on — that may be `main` or any other checkout; there is\nno branch this step must refuse to run on. Work in the repository root checkout:\nplanning steps need no worktree, and this step creates none. If you need the\ndeterministic branch contract, run:\n\n```bash\nspec-kitty agent mission branch-context --json\n```\n\nThis command reads the current checkout only and takes no `--mission` option.\n\n## Where to record findings\n\nWrite directly into `\u003Cmission_dir>\u002Fresearch.md` (that is `kitty-specs\u002F\u003Cmission_slug>\u002Fresearch.md`)\n— **create it if it does not exist yet, or extend it if it does; never truncate\nor replace existing content.** Put any supporting evidence (notebooks,\nspreadsheets, longer excerpts) under `\u003Cmission_dir>\u002Fresearch\u002F` and reference\neach file from `research.md`.\n\n## What to record\n\n- **Decisions** you have reached and the reasoning behind each one.\n- **Evidence** — sources, prior art, data — that backs each decision.\n- **Open questions** that `\u002Fspec-kitty.specify` or `\u002Fspec-kitty.plan` still\n  need to resolve.\n\nEverything you write here is available to the specify and plan steps; nothing\nhere is regenerated or discarded by them. The plan step's Phase 0 extends this\nsame `research.md`, it does not replace it.\n\n---\n\n## Research-type missions only\n\nThe section below applies **only** to mission types whose pack ships\n`research.md` \u002F `data-model.md` templates (today: the `research` mission type).\nFor every other mission type — including `software-dev` — there is no such\nscaffold: skip this section, the scaffold command creates nothing by default, and\nrecording findings by hand as described above is the whole step.\n\nOn a mission type that does ship those templates, once its plan is filled in\nyou can scaffold the remaining artifacts from the pack's templates instead of\nauthoring them by hand:\n\n```bash\nspec-kitty research --mission \u003Chandle>\n```\n\nThis creates `research.md`, `data-model.md`, `research\u002Fevidence-log.csv`, and\n`research\u002Fsource-register.csv` from the mission type's shipped templates. It\nnever overwrites an existing, non-empty file unless you pass `--force`, and it\nnever creates an empty file when no template exists for the mission type.\n\nIf this Mission is an **owned single-branch checkout** (created with\n`--owned-checkout`), scaffold into the owned checkout, never the primary:\n\n```bash\n# Owned single-branch checkouts only; do not run this for a Mission without one.\nspec-kitty research --mission \u003Chandle> --owned-checkout \u003Cowned-checkout-path>\n```\n\nRun from inside the owned checkout the selector is optional — `research`\nauto-adopts it — but passing `--owned-checkout` explicitly is safe from any\nworking directory. Not every authoring command auto-adopts; one that does not\nresolves the primary checkout, so always render the ownership selector for the\nauthoring commands an owned run invokes.\n\n---\n\n## Success Criteria\n\n- `\u003Cmission_dir>\u002Fresearch.md` exists (created or extended) and records at least\n  one decision with its rationale, or explicitly states there are none yet.\n- Any evidence you gathered is either inline in `research.md` or filed under\n  `\u003Cmission_dir>\u002Fresearch\u002F` and referenced from it.\n- Open questions that specify or plan still need to resolve are listed.\n","## Startup Upgrade Check\n\nRun this at most once per active agent session before the first Spec Kitty command workflow.\nIf you already ran `spec-kitty upgrade --agent-check --json` in this session, reuse that result and skip this block.\nDo not run or announce an upgrade check again for later Spec Kitty commands in the same session.\nOtherwise, before continuing, run:\n\n```bash\nspec-kitty upgrade --agent-check --json\n```\n\nIf JSON `action` is `none`, continue.\nIf `action` is `auto_upgrade`, run `upgrade_command` before continuing. If it fails, tell the user and continue with the current Spec Kitty version.\nIf `action` is `guidance`, show `upgrade_note` briefly, then continue.\nIf `action` is `prompt`, ask the user with the host-native question UI when available:\n\n`Spec Kitty {latest_version} is available. You are on {installed_version}. Upgrade now?`\n\nUse these choices:\n\n1. Upgrade now (recommended) - record `upgrade_now`, run `upgrade_command`, then continue.\n2. Always keep me up to date - record `always`, run `upgrade_command`, then continue.\n3. Not now - record `not_now`, then continue.\n4. Never ask again - record `never_ask`, then continue.\n\nRecord the selected choice before continuing:\n\n```bash\nspec-kitty upgrade --agent-choice \u003Cupgrade_now|always|not_now|never_ask> --agent-latest \u003Clatest_version> --json\n```\n\nIf no host-native question UI is available, present the same four choices in plain text and wait for the user.\nIn non-interactive hosts, choose `not_now` and continue.\n\n\n**Path reference rule:** When you mention directories or files, provide either the absolute path or a path relative to the project root (for example, `\u003Cmission_dir>\u002Ftasks\u002F`). Never refer to a folder by name alone.\n\n**In repos with multiple missions, always pass `--mission \u003Chandle>` to every spec-kitty command.** The `\u003Chandle>` can be the mission's `mission_id` (ULID), `mid8` (first 8 chars of the ULID), or `mission_slug`. The resolver disambiguates by `mission_id` and returns a structured `MISSION_AMBIGUOUS_SELECTOR` error on ambiguity — there is no silent fallback.\n\n## User Input\n\nThe content of the user's message that invoked this skill (everything after the skill invocation token, e.g. after `\u002Fspec-kitty.\u003Ccommand>` or `$spec-kitty.\u003Ccommand>`) is the User Input referenced elsewhere in these instructions.\n\nYou **MUST** consider this user input before proceeding (if not empty).\n\n## Goal\n\nThis is the mission's `discovery` step (not the `\u002Fspec-kitty.specify`\ndiscovery interview). Capture discovery findings — the facts, decisions, and\nopen questions gathered before a spec exists — so `\u002Fspec-kitty.specify` and\n`\u002Fspec-kitty.plan` can build on them instead of rediscovering the same\nground.\n\n## Location\n\nThis step runs before a spec or plan exists, on whatever branch your mission's\nplanning artifacts land on — that may be `main` or any other checkout; there is\nno branch this step must refuse to run on. Work in the repository root checkout:\nplanning steps need no worktree, and this step creates none. If you need the\ndeterministic branch contract, run:\n\n```bash\nspec-kitty agent mission branch-context --json\n```\n\nThis command reads the current checkout only and takes no `--mission` option.\n\n## Where to record findings\n\nWrite directly into `\u003Cmission_dir>\u002Fresearch.md` (that is `kitty-specs\u002F\u003Cmission_slug>\u002Fresearch.md`)\n— **create it if it does not exist yet, or extend it if it does; never truncate\nor replace existing content.** Put any supporting evidence (notebooks,\nspreadsheets, longer excerpts) under `\u003Cmission_dir>\u002Fresearch\u002F` and reference\neach file from `research.md`.\n\n## What to record\n\n- **Decisions** you have reached and the reasoning behind each one.\n- **Evidence** — sources, prior art, data — that backs each decision.\n- **Open questions** that `\u002Fspec-kitty.specify` or `\u002Fspec-kitty.plan` still\n  need to resolve.\n\nEverything you write here is available to the specify and plan steps; nothing\nhere is regenerated or discarded by them. The plan step's Phase 0 extends this\nsame `research.md`, it does not replace it.\n\n---\n\n## Research-type missions only\n\nThe section below applies **only** to mission types whose pack ships\n`research.md` \u002F `data-model.md` templates (today: the `research` mission type).\nFor every other mission type — including `software-dev` — there is no such\nscaffold: skip this section, the scaffold command creates nothing by default, and\nrecording findings by hand as described above is the whole step.\n\nOn a mission type that does ship those templates, once its plan is filled in\nyou can scaffold the remaining artifacts from the pack's templates instead of\nauthoring them by hand:\n\n```bash\nspec-kitty research --mission \u003Chandle>\n```\n\nThis creates `research.md`, `data-model.md`, `research\u002Fevidence-log.csv`, and\n`research\u002Fsource-register.csv` from the mission type's shipped templates. It\nnever overwrites an existing, non-empty file unless you pass `--force`, and it\nnever creates an empty file when no template exists for the mission type.\n\nIf this Mission is an **owned single-branch checkout** (created with\n`--owned-checkout`), scaffold into the owned checkout, never the primary:\n\n```bash\n# Owned single-branch checkouts only; do not run this for a Mission without one.\nspec-kitty research --mission \u003Chandle> --owned-checkout \u003Cowned-checkout-path>\n```\n\nRun from inside the owned checkout the selector is optional — `research`\nauto-adopts it — but passing `--owned-checkout` explicitly is safe from any\nworking directory. Not every authoring command auto-adopts; one that does not\nresolves the primary checkout, so always render the ownership selector for the\nauthoring commands an owned run invokes.\n\n---\n\n## Success Criteria\n\n- `\u003Cmission_dir>\u002Fresearch.md` exists (created or extended) and records at least\n  one decision with its rationale, or explicitly states there are none yet.\n- Any evidence you gathered is either inline in `research.md` or filed under\n  `\u003Cmission_dir>\u002Fresearch\u002F` and referenced from it.\n- Open questions that specify or plan still need to resolve are listed.\n",{"name":5,"description":7,"user-invocable":24},true,"main","ab710df6d6db292abd3d1288d20f338eef0ee475",".agents\u002Fskills\u002Fspec-kitty.research",0,"https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs","https:\u002F\u002Fgithub.com\u002Fspec-kitty","https:\u002F\u002Fspec-kitty.ai","2026-11-15 03:23:45",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add spec-kitty\u002Fspec-kitty-open-packs --skill spec-kitty.research",{"tool":39,"command":40},"bunx","bunx skills add spec-kitty\u002Fspec-kitty-open-packs --skill spec-kitty.research",{"tool":42,"command":43},"pnpm","pnpm dlx skills add spec-kitty\u002Fspec-kitty-open-packs --skill spec-kitty.research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspec-kitty.research\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M781XGMZZ1J569VFF53BFFRX","kitty-semi-auto","Use to take a tracker issue or a coherent issue-set through a governed delivery run that works autonomously but pauses to escalate the operator's decisions. Runs BOTH ways — in this session (local) or handed to a fresh cloud runner (cloud) — from one set of standing orders covering orientation, code grounding first, Mission-vs-Ops, the pause-and-escalate contract, brownfield discipline, and the canonical closeout to a draft PR the operator merges. Triggers: semi-auto, semi-auto dispatch, run this semi-automatically, deliver these issues semi-auto, hand this to a cloud runner, dispatch semi-auto.","https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fkitty-semi-auto\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M781XCN71TH0P1AMK99MZ042","kitty-report-debrief","Use when a maintainer asks what happened or what is open (\"what landed since Friday\", \"WTF happened with X\", a milestone overview). Collects the facts from GitHub, writes a short branded debrief for named readers, and hands the PDF back without committing it. Triggers: what landed since, WTF happened, debrief the weekend, milestone overview, exec overview of open issues, write up what shipped.","https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fkitty-report-debrief\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M781X8MDSBSEFP7HDM65A89G","kitty-mission-from-issue","Use to take one or more GitHub issues through a full governed Mission (spec, plan, tasks, implementation, review) to a green pull request flipped to ready for review, which a maintainer then merges. Triggers: mission from issue, run a mission for this issue, drive issue to PR.","https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fkitty-mission-from-issue\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M781X574X27Q630CBWXEWMBC","kitty-land-pr","Use when a ready-for-review pull request needs a maintainer to get it ready to merge. Rebases it, fixes and reviews it, updates its description, changelog and docs, and hands it back without merging by hand. Triggers: land this PR, landing pass, land PR.","https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fkitty-land-pr\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M781X0KW55NB6G0P5FKGFEX0","kitty-issue-triage","Use to triage a batch of open GitHub issues on spec-kitty\u002Fspec-kitty (default, those opened in the last 7 days). Sets type, priority, domain, parent and milestone, and reports stale, duplicate or clustered issues for an operator decision. Triggers: triage issues, triage the tracker, triage new issues.","https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fkitty-issue-triage\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M781WXTC0ACEC78PVXKB22YH","spk-team-tracker","https:\u002F\u002Fgithub.com\u002Fspec-kitty\u002Fspec-kitty-open-packs\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fspk-team-tracker\u002FSKILL.md",[],[]]