[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD5WM2RZXD8JTSD1RR90D7":3,"skill-same:01M6AD5WM2RZXD8JTSD1RR90D7":57},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M6AD5WM2RZXD8JTSD1RR90D7","speckit-preset",null,"Manage Spec Kit presets via `specify preset`. USE FOR: listing installed presets as text or JSON, installing\u002Fremoving presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling\u002Fdisabling presets, setting resolution priority, or managing preset catalogs. DO NOT USE FOR: full artifact composition stacks (use speckit-artifact), extensions (use speckit-extension), bundles (use speckit-bundle), or workflows (use speckit-workflow).","github\u002Fspec-kit-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD5D3FJESWRGNKQ1AK6THW",28,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-preset\u002FSKILL.md",[],[19,20,21,22,23,24,25,26],"preset","speckit preset","spec","workflow","workflows","search","spec kit","specify","2026-11-10 10:12:30",false,"---\nname: speckit-preset\ndescription: 'Manage Spec Kit presets via `specify preset`. USE FOR: listing installed presets as text or JSON, installing\u002Fremoving presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling\u002Fdisabling presets, setting resolution priority, or managing preset catalogs. DO NOT USE FOR: full artifact composition stacks (use speckit-artifact), extensions (use speckit-extension), bundles (use speckit-bundle), or workflows (use speckit-workflow).'\nargument-hint: '\u003Clist|add|remove|search|resolve|info|set-priority|enable|disable|catalog> [preset id]'\n---\n\n# Spec Kit — presets\n\nManage spec-kit presets with the **Specify CLI** `specify preset` command group.\nPresets bundle templates\u002Fconfiguration for a particular domain or workflow.\n\n> **Prerequisite:** needs the `specify` CLI. If `specify --version` fails, install it\n> with the **speckit-cli-setup** skill first.\n\n## When to use\n\n- Find, install, or remove a preset.\n- Check which template a preset name resolves to.\n- Enable\u002Fdisable a preset or adjust its resolution priority.\n\n## How to invoke\n\n```bash\n# Discover\nspecify preset list\nspecify preset list --json                    # machine-readable installed inventory (CLI >= 1.0.7)\nspecify preset search \u003Cquery>\nspecify preset info \u003Cid>\nspecify preset resolve \u003Cname>          # show which template a name resolves to\n\n# Install\nspecify preset add \u003Cid>\nspecify preset add --from \u003Curl>        # install from a ZIP URL\nspecify preset add --dev \u003Cpath>        # install from a local directory\nspecify preset add \u003Cid> --priority \u003Cn> # lower number = higher precedence\n\n# Lifecycle\nspecify preset enable \u003Cid>\nspecify preset disable \u003Cid>\nspecify preset set-priority \u003Cid> \u003Cn>\nspecify preset remove \u003Cid>\n\n# Catalogs (sources presets are resolved from)\nspecify preset catalog list\nspecify preset catalog add \u003Curl> --name \u003Cname> [--install-allowed]\nspecify preset catalog remove \u003Cname>\n```\n\n## Notes\n\n- Resolution priority: **lower number = higher precedence** (default `10`).\n- `specify preset list --json` requires Specify CLI **>= 1.0.7**. It preserves\n  CLI resolution order (highest precedence first) and returns `id`, `name`,\n  `description`, `version`, nullable `author`, `priority`, `enabled`, normalized\n  `source`, and `provides` counts for commands, templates, and scripts.\n- **Catalogs are added discovery-only by default.** `specify preset catalog add`\n  requires `--name` and defaults to `--no-install-allowed`; presets from a\n  discovery-only catalog can be browsed but not installed (install errors with a\n  \"discovery-only\" message). Pass `--install-allowed` to permit installs — only for\n  catalogs you trust. The `install_allowed` policy lives in the consumer's\n  `.specify\u002Fpreset-catalogs.yml`, not in the catalog's own `catalog.json`.\n- A preset can also be installed at project creation:\n  `specify init \u003Cname> --integration copilot --integration-options=\"--skills\" --script sh --preset \u003Cid>`\n  (use `--script ps` on Windows; see the speckit-init skill for the full OS-aware form and\n  why `--script` is required).\n- Use `specify preset resolve` to debug unexpected template resolution.\n- Unlike extensions\u002Fbundles, `specify preset add` does **not** scaffold skills — a\n  preset overrides the **templates** used to generate command content and is applied\n  at **init** time. `\u002Fskills reload` only matters if a regeneration actually changes\n  `SKILL.md` files under `.github\u002Fskills\u002F`.\n","# Spec Kit — presets\n\nManage spec-kit presets with the **Specify CLI** `specify preset` command group.\nPresets bundle templates\u002Fconfiguration for a particular domain or workflow.\n\n> **Prerequisite:** needs the `specify` CLI. If `specify --version` fails, install it\n> with the **speckit-cli-setup** skill first.\n\n## When to use\n\n- Find, install, or remove a preset.\n- Check which template a preset name resolves to.\n- Enable\u002Fdisable a preset or adjust its resolution priority.\n\n## How to invoke\n\n```bash\n# Discover\nspecify preset list\nspecify preset list --json                    # machine-readable installed inventory (CLI >= 1.0.7)\nspecify preset search \u003Cquery>\nspecify preset info \u003Cid>\nspecify preset resolve \u003Cname>          # show which template a name resolves to\n\n# Install\nspecify preset add \u003Cid>\nspecify preset add --from \u003Curl>        # install from a ZIP URL\nspecify preset add --dev \u003Cpath>        # install from a local directory\nspecify preset add \u003Cid> --priority \u003Cn> # lower number = higher precedence\n\n# Lifecycle\nspecify preset enable \u003Cid>\nspecify preset disable \u003Cid>\nspecify preset set-priority \u003Cid> \u003Cn>\nspecify preset remove \u003Cid>\n\n# Catalogs (sources presets are resolved from)\nspecify preset catalog list\nspecify preset catalog add \u003Curl> --name \u003Cname> [--install-allowed]\nspecify preset catalog remove \u003Cname>\n```\n\n## Notes\n\n- Resolution priority: **lower number = higher precedence** (default `10`).\n- `specify preset list --json` requires Specify CLI **>= 1.0.7**. It preserves\n  CLI resolution order (highest precedence first) and returns `id`, `name`,\n  `description`, `version`, nullable `author`, `priority`, `enabled`, normalized\n  `source`, and `provides` counts for commands, templates, and scripts.\n- **Catalogs are added discovery-only by default.** `specify preset catalog add`\n  requires `--name` and defaults to `--no-install-allowed`; presets from a\n  discovery-only catalog can be browsed but not installed (install errors with a\n  \"discovery-only\" message). Pass `--install-allowed` to permit installs — only for\n  catalogs you trust. The `install_allowed` policy lives in the consumer's\n  `.specify\u002Fpreset-catalogs.yml`, not in the catalog's own `catalog.json`.\n- A preset can also be installed at project creation:\n  `specify init \u003Cname> --integration copilot --integration-options=\"--skills\" --script sh --preset \u003Cid>`\n  (use `--script ps` on Windows; see the speckit-init skill for the full OS-aware form and\n  why `--script` is required).\n- Use `specify preset resolve` to debug unexpected template resolution.\n- Unlike extensions\u002Fbundles, `specify preset add` does **not** scaffold skills — a\n  preset overrides the **templates** used to generate command content and is applied\n  at **init** time. `\u002Fskills reload` only matters if a regeneration actually changes\n  `SKILL.md` files under `.github\u002Fskills\u002F`.\n",{"name":5,"description":7,"argument-hint":32},"\u003Clist|add|remove|search|resolve|info|set-priority|enable|disable|catalog> [preset id]","main","f77d25d39096eccac7209fd1da55056a91c4ccd7","skills\u002Fspeckit-preset",13,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-05 07:12:28",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add github\u002Fspec-kit-copilot --skill speckit-preset",{"tool":49,"command":50},"bunx","bunx skills add github\u002Fspec-kit-copilot --skill speckit-preset",{"tool":52,"command":53},"pnpm","pnpm dlx skills add github\u002Fspec-kit-copilot --skill speckit-preset","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-preset\u002FSKILL.md",true,[],[58,76,85,95,110,119],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":69,"publishedAt":27},"01M6AD63Q10N2S6YC20KT7Q192","speckit-workflow","Manage and run Spec Kit automation workflows via `specify workflow`. USE FOR: running a workflow by ID or local YAML, resuming a paused\u002Ffailed run, checking run status, listing\u002Finstalling\u002Fremoving workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use speckit-extension), presets (use speckit-preset), or bundles (use speckit-bundle).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-workflow\u002FSKILL.md",[64],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[70,22,21,71,23,72,19,73,24,74,75,25,26],"speckit workflow","automation","status","run","graph","yaml",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":83,"publishedAt":27},"01M6AD61E6FZX9N01RM1THGGGF","speckit-workflow-step","Manage Spec Kit workflow step types via `specify workflow step`. USE FOR: listing built-in and custom workflow step types, installing\u002Fremoving a custom step type from a catalog, searching\u002Fshowing step-type info, managing step-type catalog sources. DO NOT USE FOR: running or installing whole workflows (use speckit-workflow), or bundles (use speckit-bundle).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-workflow-step\u002FSKILL.md",[82],{"categoryNo":65,"categoryName":66,"taxonomyType":67,"taxonomyTypeDesc":68},[84,22,21,23,24,25,26],"speckit workflow step",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":27},"01M6AD5YVYY6XCCGDY0ZJ0ATD7","speckit-self","Check for and apply Spec Kit CLI updates via `specify self`. USE FOR: checking whether a newer specify-cli release is available, previewing an upgrade with --dry-run, upgrading the CLI in place (optionally to a pinned tag). DO NOT USE FOR: checking project tools\u002Fintegrations (use speckit-check) or managing extensions\u002Fpresets\u002Fintegrations\u002Fworkflows.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-self\u002FSKILL.md",[],[92,25,93,26,94,21,23,73],"speckit self","release","cli",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":27},"01M6AD5T7RKH20D90W5GEC6A2V","speckit-init","Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running `specify init --integration copilot --integration-options=\"--skills\"`. USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates\u002Fscripts\u002Fcommands for Copilot. DO NOT USE FOR: managing extensions\u002Fpresets\u002Fbundles of an already-initialized project (use the speckit-extension \u002F speckit-preset \u002F speckit-bundle skills instead).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-init\u002FSKILL.md",[],[102,103,104,105,21,9,106,107,19,108,109,25,26],"speckit init","init","scaffold","directory","github copilot","copilot","development","integration",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":27},"01M6AD5QWBKX4890CRHX4AY687","speckit-extension","Manage Spec Kit extensions via `specify extension`. USE FOR: listing installed extensions as text or JSON, installing\u002Fremoving\u002Fupdating extensions, searching the extension catalog, showing extension info, enabling\u002Fdisabling extensions, setting resolution priority, or managing extension catalogs. DO NOT USE FOR: artifact composition stacks (use speckit-artifact), presets (use speckit-preset), bundles (use speckit-bundle), or workflows (use speckit-workflow).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-extension\u002FSKILL.md",[],[117,19,118,24,25,26,22,21,23],"speckit extension","update",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":27},"01M6AD5NQM9P6FPN77WC51V11A","speckit-cli-setup","Detect and install the Spec Kit `specify` CLI that every other speckit skill depends on. USE FOR: checking whether `specify` is installed\u002Fon PATH, installing it when missing, fixing \"command not found: specify\", confirming the CLI is new enough (>= 0.11). DO NOT USE FOR: upgrading an already-installed CLI to a newer release (use speckit-self) or verifying project tools (use speckit-check).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fspec-kit-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-cli-setup\u002FSKILL.md",[],[94,126,127,26,25,93,21],"speckit cli setup","setup"]