speckit-bundle

Name: speckit-bundle
Author: github/spec-kit-copilot

$npx mdskill add github/spec-kit-copilot/speckit-bundle

Discover and manage Spec Kit bundles

Search for and list available bundles.
Retrieve detailed information about a specific bundle.
List all installed bundles in your project.
Install, update, or remove a specified bundle.

SKILL.md

.github/skills/speckit-bundleView on GitHub ↗

---
name: speckit-bundle
description: 'Discover, install, and author Spec Kit bundles via `specify bundle`. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and installing a bundle, managing bundle catalog sources. DO NOT USE FOR: individual extensions/presets/integrations/workflows (use their respective skills).'
argument-hint: '<search|info|list|install|update|remove|validate|build|init|catalog> [bundle id or path]'
---

# Spec Kit — bundles

Discover, install, and author Spec Kit **bundles** with the **Specify CLI**
`specify bundle` command group. A bundle is a versioned, curated set of components
(extensions, presets, integrations, workflows) installed together through each
primitive's own machinery. (Requires Specify CLI **>= 0.11**.)

> **Prerequisite:** needs the `specify` CLI. If `specify --version` fails, install it
> with the **speckit-cli-setup** skill first.

## When to use

- Find and install a bundle, or update/remove an installed one.
- Author a bundle: validate its manifest and build a distributable artifact.
- Initialize a project and install a bundle in one step.

## How to invoke

```bash
# Discover
specify bundle search <query>
specify bundle info <bundle-id>        # full metadata + fully expanded component set
specify bundle list                    # bundles installed in this project

# Install / update / remove
specify bundle install <bundle-id-or-path>     # catalog id, .zip, dir, or bundle.yml
specify bundle install <bundle-id> --integration <key> --offline
specify bundle update <bundle-id>
specify bundle remove <bundle-id>      # removes only what this bundle contributed

# Initialize a project, then optionally install a bundle
specify bundle init [<bundle-id>] [--integration <key>] [--offline]

# Authoring
specify bundle validate                # manifest well-formed + references resolve
specify bundle build --path <dir> --output <dir>   # produce a versioned .zip

# Catalog sources
specify bundle catalog list
specify bundle catalog add <url> [--policy install-allowed|discovery-only] [--priority <n>] [--id <id>]
specify bundle catalog remove <id>
```

## Notes

- `install` accepts a catalog **bundle id** or a **local path** to a `.zip`, a bundle
  directory, or a `bundle.yml`.
- `remove` only uninstalls components the bundle contributed — no collateral removals.
- Use `--offline` to avoid network access when installing from local artifacts.
- For authoring, run `specify bundle validate` before `specify bundle build`.
- A bundle installs its components through each primitive's own machinery, so any
  **extension/command** components scaffold Copilot skills under `.github/skills/`
  (in a skills-mode project). Run **`/skills reload`** to pick those up in the current
  session, or they load on the next session start.

More from github/spec-kit-copilot

Skill	Description
speckit-artifact	Inspect the effective Spec Kit artifact inventory and composition stacks via `specify artifact`. USE FOR: listing commands/templates/scripts/hooks, explaining which preset or extension layer supplies an artifact, inspecting resolution precedence and hidden layers, checking hook registration, or resolving a stack lookupId to its validated contribution. DO NOT USE FOR: installing or changing presets/extensions (use speckit-preset or speckit-extension), resolving only a preset-managed filename (use speckit-preset), or running an artifact.
speckit-check	Check the local environment for Spec Kit by running `specify check` (and `specify version`). USE FOR: verifying required tools are installed, diagnosing a broken spec-kit setup, reporting CLI version/feature capabilities. DO NOT USE FOR: installing or upgrading the CLI itself (use the speckit-self skill).
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/on 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).
speckit-extension	Manage Spec Kit extensions via `specify extension`. USE FOR: listing installed extensions as text or JSON, installing/removing/updating extensions, searching the extension catalog, showing extension info, enabling/disabling 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).
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/scripts/commands for Copilot. DO NOT USE FOR: managing extensions/presets/bundles of an already-initialized project (use the speckit-extension / speckit-preset / speckit-bundle skills instead).
speckit-preset	Manage Spec Kit presets via `specify preset`. USE FOR: listing installed presets as text or JSON, installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling 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).
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/integrations (use speckit-check) or managing extensions/presets/integrations/workflows.
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/failed run, checking run status, listing/installing/removing 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).
speckit-workflow-step	Manage Spec Kit workflow step types via `specify workflow step`. USE FOR: listing built-in and custom workflow step types, installing/removing a custom step type from a catalog, searching/showing 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).