# Install specify with Homebrew

Toolkit to help you get started with Spec-Driven Development. Version 0.15.1 via Homebrew; verified 2026-07-31.

## Install

```sh
sudo av install brew:specify
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install specify
```

  Evidence: provider-native install command

## Package facts

- **Package key:** brew:specify
- **Package manager:** Homebrew
- **Version:** 0.15.1
- **Source summary:** Toolkit to help you get started with Spec-Driven Development
- **Homepage:** <https://github.github.com/spec-kit/>
- **Repository:** <https://github.com/github/spec-kit>
- **Last updated:** 2026-07-31T16:35:56Z
- **Generated:** 2026-08-03T00:40:33+00:00

## Executables

- specify (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 0.15.1
## Project history and usage

Spec Kit is GitHub's open source toolkit for spec-driven development with AI coding agents, exposed through the specify CLI.

### Project history

The project describes Spec-Driven Development as a workflow where specifications become the center of implementation rather than disposable planning documents. Its core flow produces spec, plan, tasks, and implementation artifacts for use by AI coding agents.

### Adoption history

GitHub's documentation presents Spec Kit as an agent-neutral toolkit with 30+ integrations, community extensions, presets, and role-based bundles. GitHub API metadata for the official repository shows a public repository created in 2025 and a large star and fork count by July 2026.

### How it is used

Users install the specify CLI from the official GitHub repository, initialize a project with specify init, choose an AI coding-agent integration, and then use generated agent commands such as /speckit.specify, /speckit.plan, /speckit.tasks, and /speckit.implement.

### Why package nerds care

Spec Kit is interesting to package-manager users because its official installation path intentionally points at GitHub-based uv or pipx workflows, and the docs warn that same-named PyPI packages are not maintained by the project. It is a modern example of a CLI whose package identity and source provenance matter.

### Timeline

- 2025: The official GitHub repository was created on August 21, according to GitHub API metadata.
- 2026: Spec Kit documentation listed 30+ integrations, 105 community extensions, and 22 presets.
- 2026: Release v0.12.3 was published on July 1, according to GitHub releases.

### Related projects

- Related integrations named by the docs include GitHub Copilot, Gemini, Codex, Claude, Zed, Kiro, Forge, and generic agent support.

### Sources

- <https://api.github.com/repos/github/spec-kit>
- <https://api.github.com/repos/github/spec-kit/releases?per_page=10>
- <https://github.github.io/spec-kit/>
- <https://github.github.io/spec-kit/installation.html>
- <https://github.github.io/spec-kit/reference/core.html>


## Security Notes

No matching local secret-handling manifest was found for specify. Nucleus package metadata is still published here so future coverage has a stable package URL.



## Combined YAML source

View the package source record on GitHub. [combined/specify.yml](https://github.com/automic-vault/db/blob/main/combined/specify.yml)


## Sources

- Nucleus package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation