Motivation
Current Problems
Monolithic Growth: Adding Jira integration to core spec-kit creates:
- Large configuration files affecting all users
- Dependencies on Jira MCP server for everyone
- Merge conflicts as features accumulate
Limited Flexibility: Different organizations use different tools:
- GitHub Issues vs Jira vs Linear vs Azure DevOps
- Custom internal tools
- No way to support all without bloat
Maintenance Burden: Every integration adds:
- Documentation complexity
- Testing matrix expansion
- Breaking change surface area
Community Friction: External contributors can't easily add integrations without core repo PR approval and release cycles.
Goals
- Modularity: Core spec-kit remains lean, extensions are opt-in
- Extensibility: Clear API for building new integrations
- Independence: Extensions version/release separately from core
- Discoverability: Central catalog for finding extensions
- Safety: Validation, compatibility checks, sandboxing