This document contains potential areas for exploration and improvement for IaC Spec Kit. These are aspirational ideas, not a fixed roadmap. Priorities can shift based on community interest, feedback, and real-world usage patterns. Contributions are welcome.
The focus remains on improving templates and patterns that guide AI agents to generate better infrastructure specifications and code.
Improve the core templates based on real-world usage:
- Iterate core templates (spec, plan, tasks) based on user feedback
- Add constraints and examples to reduce AI hallucinations
- Create template complexity variants (simple vs enterprise scenarios)
- Document template design patterns (what makes effective prompts for IaC)
- Develop reusable principle files for common compliance frameworks:
- HIPAA compliance for healthcare
- PCI-DSS for payment processing
- Financial Services Cloud requirements
- SOC 2 compliance
- Industry-specific governance frameworks
Enable customization for enterprise and specialized use cases:
- User-defined template mechanism (let users create custom templates)
- Enterprise rules framework (inject organization-specific constraints)
- Custom principle file support (beyond the included examples)
- Community catalog exploration (share specs and templates)
- Plugin architecture for validation rules
- Template inheritance and composition
Streamline the developer experience with automation:
- MCP server setup automation scripts (auto-configure cloud provider MCP servers)
- Pre-commit hooks for spec/plan consistency validation
- Automated spec completeness checks
- Cost estimation guidance integrated into plan phase
- Terraform/IaC validation automation
- Setup wizards for common scenarios
Strengthen quality assurance throughout the SDD workflow:
- Enhanced template validation checkpoints
- Terraform validation improvements (tflint, checkov integration)
- Quality gate framework for infrastructure code
- Automated security scanning integration
- Compliance validation helpers
- Infrastructure testing patterns (terratest, kitchen-terraform)
Enhance compatibility and guidance across different AI agents:
- Per-model guidance and best practices (which models work best for which tasks)
- Cloud provider-specific agent feedback (which agents handle which clouds better)
- Agent compatibility testing matrix
- Model-specific prompt refinements
- Cost optimization tips per agent (token usage, context management)
Explore similar patterns for other infrastructure automation domains:
- Ansible playbook generation support
- Kubernetes manifest generation
- Helm chart templates
- Docker Compose specifications
- Service mesh configurations
- Infrastructure documentation generation
- Runbook and disaster recovery procedures
Expand cloud provider coverage and IaC tool compatibility:
- Cloud provider feedback tracking (document what works and what doesn't for each provider)
- Oracle Cloud Infrastructure (OCI) support and examples
- Alibaba Cloud support and examples
- Terragrunt integration testing and examples
- Pulumi support exploration
- Additional IaC tool compatibility (CloudFormation, ARM templates, etc.)
- Provider-specific best practices documentation
These ideas are open for anyone to explore and contribute to. Contributors can:
- Pick up any area that interests them
- Propose alternative approaches
- Share feedback on what would be most valuable
- Submit PRs for incremental improvements
- Open issues to discuss implementation approaches
For contribution guidelines, see CONTRIBUTING.md.
For questions or discussions about any of these ideas, please open a GitHub issue or start a discussion.