AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
AI 코딩 에이전트를 위한 코드베이스 인식 사양을 작성하는 도구
Spec Driven Development 🤠 Write codebase-aware specs for AI coding agents so they don't derail.
개발 도구Python · JinjaGitHub @shotgun-sh직접 설치운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Write codebase-aware specs for AI coding agents (Codex, Cursor, Claude Code) so they don't derail.
AI agents are great at small tasks but derail on big features. They forget context, rebuild things that already exist, and go off-spec halfway through.
Shotgun fixes this. It reads your entire codebase, plans the full feature upfront, then splits it into staged PRs—each with file-by-file instructions your AI agent can actually follow.
Instead of one 10k-line monster PR nobody will review, you get 5 focused PRs that ship.README 전문 보기 ↗Write codebase-aware specs for AI coding agents (Codex, Cursor, Claude Code) so they don't derail.
AI agents are great at small tasks but derail on big features. They forget context, rebuild things that already exist, and go off-spec halfway through.
Shotgun fixes this. It reads your entire codebase, plans the full feature upfront, then splits it into staged PRs—each with file-by-file instructions your AI agent can actually follow.
Instead of one 10k-line monster PR nobody will review, you get 5 focused PRs that ship.
Works great with Cursor, Claude Code, Antigravity, or Codex. BYOK or use Shotgun credits ($10 = $10 in usage).
Select your operating system below and click to view installation instructions:
Step 1: Install uv
# Using Homebrew
brew install uv
# Or using curl
curl -LsSf https://astral.sh/uv/install.sh | sh
Step 2: Run Shotgun
uvx shotgun-sh@latest
Step 1: Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
Step 2: Run Shotgun
uvx shotgun-sh@latest
Open PowerShell and run these commands:
# Set execution policy (one-time)
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force
# Install uv
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
# Add to PATH (or restart terminal)
$env:Path = "C:\Users\$env:USERNAME\.local\bin;$env:Path"
# OPTIONAL: Enable code indexing (run as Administrator)
Import-Module BitsTransfer
Start-BitsTransfer -Source "https://aka.ms/vs/17/release/vc_redist.x64.exe" -Destination "$env:TEMP\vc_redist.x64.exe"
Start-Process -FilePath "$env:TEMP\vc_redist.x64.exe" -ArgumentList "/install", "/quiet", "/norestart" -Wait
# Run Shotgun
uvx --python 3.12 shotgun-sh@latest
| Supported | Not Supported |
|---|---|
| Windows x64 (regular PCs) | 32-bit Python |
| Python 3.11-3.13 | Python 3.14+ (no wheels yet) |
Important: Run in PowerShell, not Command Prompt or VS Developer shells.
💡 Restart your terminal after installation
Why uv? It's 10-100x faster than pip and handles binary wheels reliably—no cmake/build tool errors.
Need help? View uv installation docs
When you launch Shotgun, it will guide you through:
| Step | What Happens |
|---|---|
| 1. Codebase Indexing | Builds a searchable graph of your entire repository |
| 2. LLM Setup | Configure OpenAI, Anthropic, or Gemini |
| 3. First Research | Start generating codebase-aware specs |
💡 Pro tip: Run Shotgun in your IDE's terminal for the best experience.
Click the image above to watch the full demo on YouTube
See install instructions for your platform first!
uvx shotgun-sh@latest
| Mode | How It Works | When to Use It |
|---|---|---|
| Planning (default) | Shotgun proposes an execution plan, shows each step, and asks for confirmation before running agents that change files. You get checkpoints, can refine the plan, and can confirm or skip cascaded updates when one change affects other docs. | When you want control, visibility, and the ability to refine the plan before execution. |
| Drafting | Shotgun runs the full plan in one go, without intermediate confirmations. Progress is still tracked internally, but you won’t be prompted at each step. | When you’re confident in the plan and want fast, end-to-end execution. |
The TUI opens automatically. Press Shift+Tab to switch between Planning & Drafting or / for the command palette.
Under the hood, the Router relies on specialized sub-agents. You don’t select or manage them manually.
Planning and Drafting are the only execution modes you control; everything else is handled by the Router.
Mode switching: Shift+Tab cycles through modes
| Shortcut | Action |
|---|---|
Shift+Tab | Switch modes |
/ | Open command palette |
Ctrl+C | Cancel operation (or copy if text selected) |
Escape | Exit Q&A / stop agent |
Ctrl+U | View usage stats |
| Do This | Not This |
|---|---|
✅ Research how we handle auth | ❌ Jump straight to building |
✅ Shotgun please ask me questions first | ❌ Assume Shotgun knows your needs |
✅ I'm working on payments, need refunds | ❌ Add refunds (no context) |
| ✅ Start in Planning mode, let Shotgun propose and refine a plan with you, then run it | ❌ Blast everything in one go without reviewing the plan first (unless you intentionally switch to Drafting mode) |
Result: Your AI coding agent gets complete context—what exists, why, and what to build.
Note: CLI available in docs/CLI.md, but TUI is recommended.
The Research agent can fetch up-to-date library documentation via Context7. When configured, the agent will prefer Context7 over web search for documentation lookups.
To enable it, set your Context7 API key:
shotgun config set-context7 --api-key <your-context7-api-key>
To remove it:
shotgun config clear-context7
Sharing specs to a workspace is available on paid Shotgun plans.
Shotgun lets you share specs externally by publishing them to a workspace. This creates a versioned, shareable snapshot your team can access outside the repo.
/ → select Share specs to workspace.shotgun/ filesYour local .shotgun/*.md files remain unchanged.
The workspace contains a shareable, versioned snapshot of the spec.
We had to implement payments. Cursor, Claude Code, and Copilot all suggested building a custom payment proxy — 3-4 weeks of development.
⭐ Shotgun's research found LiteLLM Proxy instead—30 minutes to discover, 5 days to deploy, first customer in 14 hours.
80% less dev time. Near-zero technical debt.
📚 Want to see a detailed example? Check out our Case Study showing Shotgun in action on a real-world project.
Q: Does Shotgun collect any stats or data?
A: We only gather minimal, anonymous events (e.g., install, server start, tool call). We don't collect the content itself—only that an event occurred. We use PostHog for analytics and error reporting to improve stability.
Q: Does my code leave my computer when indexing?
A: No. When you index your codebase, all indexing happens locally on your machine. The index is stored in ~/.shotgun-sh/codebases/ and never sent to any server. Your code stays on your computer.
Q: Local LLMs?
A: Planned. We'll publish compatibility notes and local provider integrations.
Q: What LLM providers are supported?
A: Currently OpenAI, Anthropic (Claude), and Google Gemini. Local LLM support is on the roadmap.
Q: Can I use Shotgun offline?
A: You need an internet connection for LLM API calls, but your codebase stays local.
Q: How does the code graph work?
A: Shotgun indexes your codebase using tree-sitter for accurate parsing and creates a searchable graph of your code structure, dependencies, and relationships.
Shotgun is open-source and we welcome contributions. Whether you're fixing bugs, proposing features, improving docs, or spreading the word—we'd love to have you as part of the community.
Not sure where to start? Join our Discord and we'll help you get started!
Planning → Drafting — Two execution modes that give AI agents the full picture, backed by internal phases for Research → Specify → Plan → Tasks → Export.
uvx shotgun-sh@latest
License: MIT | Python: 3.11+ | Homepage: shotgun.sh
uv tool uninstall shotgun-sh