Presets
Presets customize how Spec Kit works — overriding templates, commands, and terminology without changing any tooling. They let you enforce organizational standards, adapt the workflow to your methodology, or localize the entire experience. Multiple presets can be stacked with priority ordering.
Search Available Presets
specify preset search [query]| Option | Description |
|---|---|
--tag | Filter by tag |
--author | Filter by author |
Searches all active catalogs for presets matching the query. Without a query, lists all available presets.
Install a Preset
specify preset add [<preset_id>]| Option | Description |
|---|---|
--dev <path> | Install from a local directory (for development) |
--from <url> | Install from a custom URL instead of the catalog |
--priority <N> | Resolution priority (default: 10; lower = higher precedence) |
Installs a preset from the catalog, a URL, or a local directory. Preset commands are automatically registered with the currently installed AI coding agent integration.
Note: All preset commands require a project already initialized with
specify init.
Remove a Preset
specify preset remove <preset_id>Removes an installed preset and cleans up its registered commands.
List Installed Presets
specify preset list
specify preset list --jsonLists installed presets with their versions, descriptions, template counts, and current status.
--json writes a JSON array to stdout. Every item has the keys id, name, description, version, author, priority, enabled, source, and provides. author is null when absent; source is \{"kind":"local"\} for local, legacy, or malformed provenance, or