I built a CLI to make spec-driven development usable
Hi HN ,
I built SpecPilot to solve a problem I kept running into: spec-first development sounds great, but most tools are either too heavy or too rigid for day-to-day dev work.
SpecPilot is a small, open-source CLI that helps you: - define specs first (Markdown-based) - keep them versioned alongside code - scaffold projects and workflows from those specs
I built it for myself and my team, and decided to open-source it.
Website: https://specpilot.dev GitHub: https://github.com/girishr/SpecPilot
Would really appreciate feedback on: - whether this fits into your workflow - what feels unnecessary - what’s missing for real-world use
Happy to answer any questions.
Some context:
I intentionally avoided OpenAPI / heavy spec formats. The goal was: - something devs actually write - easy to diff in PRs - flexible enough for non-API workflows too
If you’ve tried spec-first approaches before and bounced off them, I’d love to know what didn’t work for you.