Hi HN,

I built SpecOps, an open-source CLI framework inspired by GitHub's Spec Kit approach, that brings Spec-Driven Development to Infrastructure as Code.

The problem: Most IaC projects start with ad-hoc scripting — jumping straight into Terraform/Ansible without clear specs.

SpecOps enforces a structured workflow:

Idea → Specification → Plan → Tasks → Implementation

It works with AI coding agents (Claude Code, GitHub Copilot, Cursor, Gemini CLI, Windsurf, and 12+ others) to guide you through each phase. You define what you want, plan how to build it, break it into tasks, then implement — with AI assistance at every step.

How it works:

specops init my-infrastructure --ai claude cd my-infrastructure # 1. /specops.constitution – Establish infrastructure principles # 2. /specops.specify – Define requirements # 3. /specops.plan – Create technical plan # 4. /specops.tasks – Generate task breakdown # 5. /specops.implement – Execute with AI

Key points:

Technology agnostic (Terraform, Pulumi, CloudFormation, Ansible, etc.) Supports 17+ AI coding agents out of the box Generates project structure, templates, and agent-specific command files Validation checkpoints after each deployment phase Rollback procedures documented per phase MIT licensed Inspired by GitHub's Spec Kit approach, adapted for infrastructure engineering.

GitHub: https://github.com/dotlabshq/spec-ops

Install: uv tool install specops-cli --from git+https://github.com/dotlabshq/spec-ops.git

I'd love to hear your feedback — especially from teams managing complex infrastructure. What does your IaC workflow look like? Would a spec-first approach fit your process?

Show HN: SpecOps – Spec-Driven Development for Infrastructure as Code