Should spec-kit support Homebrew as an installation option?

[RbBtSn0w]

I would like to open a discussion about supporting Homebrew as an additional installation path for spec-kit / specify-cli.

The current README primarily recommends:

uv tool install specify-cli --from git+https://github.com/github/spec-kit.git

That is a solid path, but for many macOS developers, brew install ... is the default expectation for CLI tools.

Why discuss this

• lower installation friction for macOS users already using Homebrew
• provide a familiar install/upgrade/uninstall workflow
• improve discoverability for users who may not already know uv
• keep uv as the main path while offering Homebrew as an additional option

Possible directions

1. Maintain an official Homebrew tap.
2. Package from PyPI or tagged GitHub release artifacts.
3. Add Homebrew to the README as an optional install path, not a replacement.
4. Revisit Homebrew/core only if maintenance burden stays low.

Open questions

• Is the release process already compatible with Homebrew packaging?
• Would maintainers be open to an official tap, or is this out of scope?
• If contributions are welcome, are there packaging/versioning constraints contributors should account for?

I previously opened an issue for this topic, but this seems better suited to Discussions since it is mainly a product/distribution conversation rather than a concrete bug report.

Related issue: #1903

[shmygol]

Looks like there is already a formula for spec-kit, but it's called Specify.