IntentDocs vs GitHub spec-kit (2026)
Disclosure first: we build IntentDocs, so this comparison has a side. We've tried to earn your trust the only way that works — by marking the rows GitHub spec-kitwins, and saying plainly when it's the better choice.
GitHub spec-kit is a open-source spec-driven development toolkit; IntentDocs is a spec-driven development platform where an AI interview produces a visual story map, data model, and build order that your coding agent builds from over MCP, with an audit trail of built versus planned. Choose GitHub spec-kit if you want free, open-source, markdown-in-repo specs driven from the terminal. Choose IntentDocs if you want an AI interview to extract the spec, a visual story map non-developers can read, and built-vs-planned tracking once your agent starts building.
What is GitHub spec-kit?
spec-kit is GitHub's free, open-source toolkit for spec-driven development. Install the CLI and your coding agent gets a slash-command workflow — constitution, specify, plan, tasks, implement — producing markdown spec files in your repo that the agent executes against. It works with Copilot, Claude Code, Cursor, Gemini CLI, and most other agents, and has the largest community and third-party writing of any tool in the category.
What is IntentDocs?
IntentDocs is a spec-driven development platform: an AI interview turns your idea into a structured spec — a visual story map, data model, and build order — and your coding agent (Claude Code, Cursor, or any MCP client) builds from it over MCP, with an audit trail of what was built versus what was planned.
IntentDocs vs GitHub spec-kit: feature by feature
A ✓ marks our honest call on who wins each row — including the ones we lose.
| Feature | IntentDocs | GitHub spec-kit |
|---|---|---|
| Cost | £12/month after a 7-day trial | Free, open source |
| Where specs live | In IntentDocs, synced to your repo via CLI/MCP | Markdown files versioned natively in your repo |
| Getting the spec out of your head | AI interview extracts it, then structures it | Slash commands structure what you write — the blank page is yours |
| Readable by non-developers | Visual story map a founder or PM can read and reshape | Markdown in an editor — fine for devs, opaque for everyone else |
| After the build starts | Agent syncs progress back — audit trail of built-versus-planned | No feedback loop; drift between spec and code is invisible |
| Agent support | Any MCP client, plus the CLI | Copilot, Claude Code, Cursor, Gemini CLI, and most others |
| Community and ecosystem | Young | Largest in the category — most tutorials, most third-party writing |
Pricing
GitHub spec-kit (August 2026):
- Open source: Free — MIT-licensed CLI; you pay only for your own agent/LLM usage
IntentDocs: 7-day free trial, no card required. Pro is £12/month (or £120/year, equivalent to £10/month). Team is £15 per seat/month (or £144/seat/year), minimum 2 seats. Enterprise is custom. Full details on the pricing page.
Which should you choose?
Choose GitHub spec-kit when…
- You're a terminal-native developer and markdown-in-repo is exactly where you want specs.
- You want free and open source, with no new SaaS surface to adopt.
- Specs must be versioned in git next to the code they describe.
- You lean on community: spec-kit has the most tutorials and third-party writing in the category.
Choose IntentDocs when…
- You want an interview to pull the spec out of your head instead of facing a blank specify command.
- A founder, PM, or client needs to read and shape the spec — a story map beats markdown for them.
- You want to know what the agent actually built against the plan, not just what the plan said.
- You're starting from an existing codebase and want the spec generated for you via GitHub import.
The honest verdict
spec-kit earned its place as the open-source default, and if you're a developer who wants free, files-in-repo, terminal-native specs, you should probably just use it — that's the honest answer. IntentDocs is for the people spec-kit quietly excludes: builders who want an interview to do the extraction, a visual map their co-founder can read, and a spec that stays reconciled with what the agent actually ships.
Frequently asked questions
Is GitHub spec-kit really free? Yes — it's MIT-licensed open source. You pay only for the coding agent and LLM usage you were already paying for. IntentDocs is a paid product (£12/month after a 7-day trial), so spec-kit wins any pure-cost comparison.
Can I use spec-kit and IntentDocs together? Technically yes, but you'd have two sources of truth for the same spec, which defeats the point. Pick one: spec-kit if the spec should live as markdown in your repo, IntentDocs if it should live as a story map your agent connects to over MCP.
Which should a non-technical founder pick? Not spec-kit — it assumes you're comfortable in a terminal and reviewing markdown diffs. IntentDocs's interview-and-story-map flow is built for exactly this case. (Kiro and CodeGuide are also more approachable than spec-kit here.)
Does IntentDocs work with the same agents as spec-kit? Largely, yes. spec-kit supports Copilot, Claude Code, Cursor, Gemini CLI, and more. IntentDocs connects over MCP — Claude Code, Cursor, and any MCP client — plus its CLI. If your agent speaks MCP, both tools can serve it.
Keep reading
- The GitHub spec-kit alternative guide — the switching-focused version of this page.
- The best spec-driven development tools in 2026 — the full field, including tools neither of us competes with.
Facts about GitHub spec-kit verified August 2026 against their published pricing and documentation. Spotted something out of date? Tell us and we'll fix it.
Ready to build what you intended?
Turn your idea into a structured spec and hand it to Claude Code or Cursor over MCP — with an audit trail of built versus planned.
Start free →7-day free trial · no card required