Build your specs before your code
Vibe coding starts strong but deteriorates as projects grow complex.
SpecPilot uses Specification-Driven Development (SDD) to generate a complete .specs/ workspace - keeping your AI aligned with your architecture, standards, and vision from the first prompt to production.
Step-by-step wizard~5 minNo login requiredRuns fully offline, nothing sent to our servers
Next.js
TS / JS
FastAPI
Python
React Native
JS / TS
Node/Express
TS / JS
Generated .specs/ Works with your AI coding tool
Complete Engineering Bundle
A fully structured .specs/ folder ready for your IDE or AI Agent. 12 files generated.
requirements.md
Functional & non-functional requirements, user stories, and acceptance criteria.
project.yaml
Project config, rules, and AI agent context. MANDATED — read on every AI session.
architecture.md
System design decisions, patterns, and component hierarchy.
api.yaml
CLI / REST / GraphQL interface specification in structured YAML.
roadmap.md
Release milestones and objectives across project phases.
tasks.md
Sprint tracker with backlog, current, and completed columns.
prompts.md
AI interaction log. MANDATED — must be updated every coding session.
threat-model.md
Threat inventory with impact, likelihood, and mitigation for each risk.
context.md
Architecture decisions, ADRs, and design rationale log for the project.
onboarding.md
A ready-to-paste prompt that briefs your AI agent — populates every spec file, then gets deleted.
tests.md
Test strategy, coverage targets, and quality acceptance criteria.
security-decisions.md
Security architecture decisions and risk-level mitigations accepted per review.
The 4-Step Alignment Flow
Launch Wizard
Start the init flow at init.specpilot.dev
Answer Questions
Provide structured input via our guided multi-step chat interface.
Scaffold Specs
SpecPilot scaffolds your .specs/ folder and a ready-to-use onboarding prompt.
AI Generation
Paste the prompt into your AI IDE or agent to generate your complete specs.
Prefer the CLI?
The SpecPilot CLI generates the same .specs/ structure from your terminal — useful for teams that want spec init in existing scripts or CI setup.
Requirements
| Command | Alias | What it does |
|---|---|---|
| specpilot init | i | Initialize new SDD project |
| specpilot init --dry-run | — | Preview files that would be created without writing |
| specpilot add-specs | add | Add specs to existing project |
| specpilot validate | v | Validate specification files |
| specpilot archive | ar | Archive oversized prompts.md / tasks.md entries |
| specpilot backfill | bf | Backfill missing mandates into existing projects |
| specpilot list | ls | Show available templates |
| specpilot migrate | m | Convert legacy .project-spec folder (rarely needed) |
| specpilot refine | ref | Refine project specifications from natural language description |

IDE and agent support
Config generated for your agent, automatically.
Pick your AI coding tool in Step 2. The wizard generates the right config file, plus 8 /specpilot-* slash/workflow commands (status, reanchor, report, sync, refine, validate, archive, backfill) in the format your agent natively supports — no manual setup.
- GitHub Copilotconfig → .github/copilot-instructions.mdcommands → .github/prompts/specpilot-*.md
- Cursorconfig → .cursor/rules/specpilot.mdccommands → .cursor/commands/specpilot-*.md
- Windsurfconfig → .windsurfrulescommands → .windsurf/workflows/specpilot-*.md
- Antigravityconfig → .antigravity/rules.mdcommands → .agent/workflows/specpilot-*.md
- Claude Codeconfig → CLAUDE.mdcommands → .claude/commands/specpilot-*.mdskill → .claude/skills/specpilot-project/SKILL.md
- Codexconfig → .github/copilot-instructions.mdcommands → .codex/prompts/specpilot-*.mdskill → CODEX_INSTRUCTIONS.md
Claude Code additionally gets a Claude Skill (.claude/skills/specpilot-project/SKILL.md) for project-context lookup, and Codex gets a standalone CODEX_INSTRUCTIONS.md at the project root.
Get started
Stop vibe-coding.
Start spec-first.
5 minutes with the wizard. 12 files your AI agent can actually use.