The Evolution of Spec-Driven Tooling
GitHub's open-source Spec-Kit helped popularize markdown-based specifications for AI coding. However, CLI-only templates require developers to manually write boilerplate specifications, manually debug acceptance criteria syntax, and manually copy files into IDE contexts.
MySpec takes a different approach: an automated Senior Architect AI engine that interviews you in 2 minutes, extracts hidden edge cases, formats requirements using EARS+ syntax, and streams the live bundle directly into Cursor, Claude Code, and Devin via MCP.
Comprehensive Feature Comparison
| Feature | GitHub Spec-Kit | MySpec |
|---|---|---|
| User Interface | Terminal CLI only | Interactive Web App + MCP Server |
| Spec Generation | Manual Markdown typing | 2-Min Socratic AI Senior Architect Interview |
| Requirements Review | /speckit.analyze audit and /speckit.checklist, run on demand | EARS+ reviewer agent on the MySpec requirements stage |
| Diagram Generation | No diagram step in the templates | Live Mermaid.js System Diagrams |
| IDE Streaming | Manual file reading | Native Model Context Protocol (@myspec/mcp-server) |
| Brownfield Codebase Support | /speckit.converge assesses an existing codebase | Reads your repo via reverse-MCP or a mounted folder; writes proposal.md + requirements delta (or OpenSpec changes) |
| Spec Kit File Layout | Native | Native too - a Spec Kit workflow writes specs/memory/constitution.md and specs/NNN-feature/spec.md, plan.md, tasks.md |
Keep Your Spec Kit Layout - Add the Architect
You do not have to choose. MySpec ships a Spec Kit-compatible generate workflow: the AI Architect interviews you, then writes specs/memory/constitution.md once per project and specs/001-feature/spec.md, plan.md, and tasks.md per feature - the same files the specify CLI and its slash commands read.
Already have Spec Kit files in a repo? Bring them into a MySpec project from your AI editor through the MCP server, then keep editing on either side:
npx -y @myspec/mcp-server login# 2. In Cursor / Claude Code, with the MySpec MCP server connected:
"Upload specs/001-photo-albums/spec.md to my MySpec project with upload_spec_file"# 3. Pull the reviewed bundle back into .specs/ whenever it changes
download_spec_file(file_id) → .specs/001-photo-albums/spec.md Switch to MySpec
Generate your first 4-file spec bundle with zero CLI boilerplate.