Summary
Currently there is no way to select which extensions to enable during specify init. The git extension is hardcoded to auto-install, and all other extensions must be added post-init via specify extension add. Before the git extension stops being enabled by default (planned for 1.0.0), users need a way to opt in at init time.
Proposed behavior
Add an --extension flag (repeatable) to specify init that accepts bundled extension names, local paths, or URLs:
# Bundled extension by name
specify init my-project --integration copilot --extension git
# Multiple extensions
specify init my-project --extension git --extension selftest
# Local path
specify init my-project --extension ./my-extensions/custom-ext
# URL
specify init my-project --extension https://example.com/extensions/my-ext.tar.gz
Acceptance criteria
Summary
Currently there is no way to select which extensions to enable during
specify init. The git extension is hardcoded to auto-install, and all other extensions must be added post-init viaspecify extension add. Before the git extension stops being enabled by default (planned for 1.0.0), users need a way to opt in at init time.Proposed behavior
Add an
--extensionflag (repeatable) tospecify initthat accepts bundled extension names, local paths, or URLs:Acceptance criteria
specify initaccepts--extension <value>(repeatable)--integration,--preset, etc.)