This is a submission for the GitHub Copilot CLI Challenge
What I Built
I built SpecPilot - an open-source, spec-driven development tool that helps engineers move away from “vibe coding” and toward intent-first software design.
SpecPilot sits at the intersection of AI and engineering rigor. Instead of jumping straight from prompt → code → fix → repeat, it encourages teams to slow down just enough to define:
- Clear intent
- Constraints
- Acceptance criteria
- Architectural boundaries
before code is generated.
This project is personal for me. Over the months, I’ve seen how AI doesn’t create bad engineering practices—it amplifies existing ones. SpecPilot is my attempt to create a lightweight but opinionated workflow that helps teams use AI responsibly, without turning software into a fragile house of cards.
SpecPilot is fully open source and available on GitHub:
👉 https://github.com/girishr/SpecPilot
👉 https://specpilot.dev
Demo
- GitHub Repository: https://github.com/girishr/SpecPilot
- Website: https://specpilot.dev (Its got a terminal emulator that shows how the tool works)
The repo includes:
- CLI workflows
- Example specs
- End-to-end flows showing how specs evolve into implementation-ready artifacts
I’m actively iterating in the open, so the demo evolves as the project grows. (you can check out the .spec folder in https://github.com/girishr/SpecPilot/blob/main/.specs/planning/tasks.md to see what is planned)
My Experience with GitHub Copilot CLI
GitHub Copilot CLI played a meaningful role in building SpecPilot—but it wasn’t the only tool in the loop.
I used Copilot CLI primarily for:
- Exploring CLI command flows quickly
- Generating shell scripts and scaffolding logic
- Rapid iteration while staying inside the terminal
- Sanity-checking ideas without breaking context
At the same time, I paired it with:
- GitHub Copilot Chat inside VS Code for deeper reasoning, refactoring, and architectural discussion
- Multiple models depending on the task:
- Claude Sonnet for structured reasoning and spec clarity
- GPT-5.2 Codex for implementation-heavy work
- Grok Code (free) for fast experimentation and alternate perspectives
This mix-and-match approach felt natural. Different problems benefit from different strengths, and Copilot CLI fit nicely as a terminal-native accelerator, not a replacement for thinking.
One thing I appreciated was how Copilot CLI reduced friction. It didn’t try to “own” the workflow—it supported it. That aligns well with SpecPilot’s philosophy: AI should assist intent, not replace it.
SpecPilot vs GitHub SpecKit
I’m aware that GitHub already offers a similar concept with SpecKit.
SpecPilot wasn’t built as a competitor.
It exists because I personally felt there were a few gaps and ideas not fully addressed by SpecKit—particularly around opinionated workflows, extensibility, and how specs evolve alongside AI-assisted coding.
That said, both tools are aligned on the same core principle:
Better specs lead to better software.
I see SpecKit and SpecPilot as different interpretations of spec-driven development, each with its own philosophy and trade-offs. Choice is a good thing, especially in a space as young and fast-moving as AI-assisted engineering.
Closing Thoughts
This challenge wasn’t just about using Copilot—it was about understanding where AI fits best in real developer workflows.
For me, Copilot CLI shines when it:
- Reduces context switching
- Speeds up experimentation
- Lets ideas flow without ceremony
SpecPilot is still evolving, but GitHub Copilot—especially in the CLI—has already become a trusted companion in that journey.
Thanks to the GitHub and DEV teams for running this challenge. It’s exactly the kind of space where thoughtful, open experimentation belongs.
Top comments (2)
I love the concept around specpilot.
I happen to read about your work on GitHub but I've actually searched for you and I finally found you.
I'm a fan actually. Keep up the good work 💪
Hey Faith, thanks very much for the kind words about SpecPilot.dev. I appreciate it.