Spec Driven Development for Developers and AI Agents.
Turn endless iterations into one-shot features.
Shotgun writes codebase-aware specs for AI coding agents. We index your entire repo, research how features should fit your architecture, and generate technical specs that keep Cursor, Claude Code, and Lovable on track.
Export to AGENTS.md. Your AI agent builds correctly the first time instead of derailing halfway through.
Open source CLI for developers working with AI coding agents.
Shotgun CLI
Howdy, partners! 🤠
AI coding tools like Cursor, Claude Code, and Lovable are getting stronger by the day. But out here on the frontier, we’ve all seen the same trouble:
Code that looks right but won’t run
Features that miss the intent
Stacks and architectures you’d never saddle up with
That’s what happens when you send your AI riding blind. Garbage in → garbage out.
So we built Shotgun — your codebase-aware spec engine for AI code-gen tools. Think of it as your AI posse:
The Researcher scouts the landscape
The Architect maps your system
The Product Strategist charts the user journey
The Spec Writer wrangles it all into a buildable doc
And now, Shotgun goes one step further — it can actually read your repo, grounding specs and diagrams in your real codebase. Every artifact can be previewed in a clean Webview and — only if you choose — shared with your team or the wider campfire.
🔑 Spec → Code (export to Cursor, Claude Code, or Lovable with a single command)
🔑 Local-first (your keys, your data)
🔑 Multi-agent (a full posse working together)
🔑 Repo-aware (specs that fit your system, not generic templates)
🔑 On-demand sharing (you decide what leaves your machine)
Shotgun is still early, and we’d love for you to ride with us. Try it out, break it, and tell us where the trails should lead next.
Excited to hear what you think! 🚀
ScaryStories Live
@barticz Congrats on the launch, repo-aware specs feel like a real unlock. Do you see Shotgun evolving more as a daily copilot for devs, or as a higher-level planning tool teams use before coding starts?
Shotgun CLI
@tonyabracadabra Thanks 🙏 You nailed the distinction. Today Shotgun is focused on being that planning layer for devs — turning open questions into repo-aware specs that can be fed to tools like Cursor or Claude before coding starts.
Team-focused workflows are on our roadmap after Alpha — things like shared artifacts, collaboration modes, and tighter planning loops. Long term, we see Shotgun supporting both individual devs day-to-day and teams who need a common source of truth before they ship.
Would love to know: in your experience, does the bigger pain sit at the individual level (daily coding clarity) or the team level (alignment + planning)?
Interesting tool! But I noticed there’s already a more advanced and popular product with the same name. Could this be borrowing from an existing idea? It would be great to understand how your product differentiates itself. https://github.com/glebkudr/shot...
@sergey_g That's what I thought this was. I'm curious what the response is. Definitely will give this a shot (no pun intended lol) though.
Shotgun CLI
@sergey_g it didn't exist when we started :)
@sergey_g @barticz Did you have a public release in 2023? I think the public release of the app is important because while you are developing it exclusively for yourself, you can even call it Google :)
UPD:
Also this picture is meaningless, since the repository can be renamed, it seems to me that it is worth starting from the moment of domain registration
Hey did you really steal this guy idea? https://github.com/glebkudr/shotgun_code/
I can't believe
Shotgun CLI
@timur__khakhalev it didn't exist when we started :)
@barticz it doesn't approve anything. show first commits :)
I know Shotgun as a different coding tool. You shouldn't use this name – it's bad karma! 👻
https://github.com/glebkudr/shotgun_code
Shotgun CLI
@dmitry_kuchev1 it did exist when we started :)
Alice
Spec-driven development with AI is my favorite way to work right now. But going from idea to spec is a daunting process. Testing it straight away. Big congrats on the launch, keep rocking cowboys!
Shotgun CLI
@gregrog Thanks Greg 🤠 Totally agree — spec-driven dev with AI is powerful, but starting from a blank page can feel overwhelming. That’s exactly where we’re aiming to help: turning open-ended ideas into structured specs that you can actually build from.
Excited to hear what you think once you test it — curious which part of the spec flow (PRDs, trade-offs, architectures) feels most valuable in your workflow?
Planning is the bottleneck for AI coding tools and you're tackling it directly. Specs that match intent? Brilliant. Local-first is reassuring too. Excited to see how this plays with Cursor and Claude Code.
Shotgun CLI
@angelina__ashley Thanks Iris 🙌 code is rarely the problem, it’s always “what are we even building?” That’s why we went with specs that tie back to the repo. Cursor/Claude can still do the coding, but at least now they’re starting from something solid.
Congrats! 💪 Fingers crossed!
Shotgun CLI
@mateusz_kowalczyk2 thank you so much!!