A collection of community-contributed extensions for spec-kit that enhance the Spec-Driven Development workflow with additional commands and capabilities.
This repository also serves as an incubation space for new commands—allowing you to develop, test, and gather community feedback on experimental features before potentially proposing them as additions to the core spec-kit repository.
Spec-Kit is a structured approach to software development that flips the traditional model—specifications become executable, directly generating working implementations rather than just guiding them. Learn more at the official spec-kit repository.
Analyze how your current feature aligns with existing features using systems thinking to identify conflicts, dependencies, and emergent behaviors before implementation.
Status: ✅ Ready to use
Compatible with: spec-kit (latest version with /speckit.* command structure)
Supported agents: Claude, GitHub Copilot, Cursor, Gemini, and others
Quick Install:
# Clone and run installer
git clone https://github.com/polarizertech/spec-kit-extensions.git
cd spec-kit-extensions
# Bash/Zsh
./install.sh cross-feature /path/to/your/spec-kit-project
# PowerShell
.\install.ps1 cross-feature C:\path\to\your\spec-kit-projectspec-kit-extensions/
├── install.sh # Centralized installer (bash)
├── install.ps1 # Centralized installer (PowerShell)
├── extensions/
│ └── cross-feature/ # Cross-feature alignment extension
│ ├── README.md # Extension documentation
│ ├── extension.yaml # Extension manifest
│ ├── addon/ # Files to be installed
│ │ ├── commands/ # Command definitions
│ │ ├── scripts/ # Supporting scripts
│ │ └── templates/ # Templates
│ └── examples/ # Example outputs
└── scripts/ # Shared utilities
Extensions are drop-in additions to your spec-kit project that add new slash commands. Each extension includes:
- Extension manifest (
extension.yaml) - Declares files and metadata - Command definitions (e.g.,
addon/commands/speckit.extn.cross-feature.md) - Supporting scripts (e.g.,
addon/scripts/bash/...) - Templates (e.g.,
addon/templates/...) - Documentation (README, examples)
Extensions follow the /speckit.extn.* naming convention to distinguish them from core spec-kit commands (/speckit.*).
The centralized installer reads each extension's manifest and automatically installs files to the correct locations in your project.
Bash/Zsh (macOS, Linux, WSL):
# Clone this repository
git clone https://github.com/polarizertech/spec-kit-extensions.git
cd spec-kit-extensions
# Install specific extension
./install.sh cross-feature /path/to/your/spec-kit-project
# Or install all extensions
./install.sh --all /path/to/your/spec-kit-project
# List available extensions
./install.sh --listPowerShell (Windows):
# Clone this repository
git clone https://github.com/polarizertech/spec-kit-extensions.git
cd spec-kit-extensions
# Install specific extension
.\install.ps1 cross-feature C:\path\to\your\spec-kit-project
# Or install all extensions
.\install.ps1 -All C:\path\to\your\spec-kit-project
# List available extensions
.\install.ps1 -ListWant to contribute an extension? Here's what you need:
- Create a directory under
extensions/YOUR_EXTENSION_NAME/ - Create an
extension.yamlmanifest with minimal required fields - Add your command files, scripts, and templates under
addon/ - Write comprehensive documentation (README.md)
- Add usage examples
- Submit a pull request
That's it! No need to write installers - the centralized installer handles everything based on your manifest.
💡 Incubation Path to Core Spec-Kit
This repository is an excellent place to incubate experimental commands before proposing them to the official spec-kit repository. You can:
- Develop and refine your command with real-world usage
- Gather community feedback and iterate on the design
- Build evidence of utility and adoption
- Mature your extension before submitting a PR to spec-kit
Successful extensions that prove valuable may graduate to become core spec-kit commands (
/speckit.*).
See CONTRIBUTING.md for detailed guidelines and manifest format.
Extensions are tested with:
- spec-kit: Latest version with
/speckit.*command structure - AI Agents: Claude, GitHub Copilot, Cursor, Gemini, Qwen, OpenCode, Windsurf, and others
- Platforms: macOS, Linux, Windows (via WSL or PowerShell)
- Issues: Report problems or request features via GitHub Issues
- Discussions: Ask questions in GitHub Discussions
- Spec-Kit Issues: For core spec-kit issues, use the official repository
Contributions are welcome! Whether you want to:
- Add a new extension
- Improve existing extensions
- Fix bugs
- Enhance documentation
Please read CONTRIBUTING.md for guidelines.
This project is licensed under the MIT License - see the LICENSE file for details.
- The spec-kit team for creating the foundation
- All contributors who have added extensions and improvements
- The AI-assisted development community
These are community-contributed extensions and are not officially maintained by the spec-kit team. While we strive for quality and compatibility, please test thoroughly before using in production environments.
Published at: https://github.com/polarizertech/spec-kit-extensions