# Installer specify avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de specify pour les workflows d'agents IA.

## installation

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

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install specify
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:specify
- **Gestionnaire de paquets:** Homebrew
- **Version:** 0.15.1
- **Résumé source:** Toolkit to help you get started with Spec-Driven Development
- **Page d'accueil:** <https://github.github.com/spec-kit/>
- **Dépôt:** <https://github.com/github/spec-kit>
- **Dernière mise à jour:** 2026-07-31T16:35:56Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- specify (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 0.15.1
## Historique du projet et usages

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

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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.

### Chronologie

- 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>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour specify. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## Combined YAML source

View the package source record on GitHub. [combined/specify.yml](https://github.com/mxcl/pkgdb/blob/main/combined/specify.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph