Spec-Driven Development
The methodology where the specification is the primary development artifact.
SDD is a methodology where the requirements document isn't passive documentation — it's an executable contract from which code, tests, and evidence are derived. If it's not in the spec, it doesn't get built. If it's in the spec, it gets verified.
From vibe coding to spec-driven
Since Andrej Karpathy coined the term in February 2025, "vibe coding" has become normalized: asking AI to generate code without structure, without a plan, without verification. It works for prototypes. For production, it creates exponential technical debt.
The biggest risk in a software project isn't technical. It's that business and development speak different languages. What the client signs off as a proposal and what they receive as a final product are different things.
Spec-Driven Development closes that gap: the specification is an executable contract from which code is derived. Not passive documentation — a living artifact the machine understands and enforces.
Maturity Levels
Spec-first
A spec is written before coding. Used during the task.
Spec-anchored
The spec is maintained after the task for evolution and maintenance.
Spec-as-source
The spec IS the primary artifact. Humans never touch the code.
SDD Frameworks
| Framework | Main limitation |
|---|---|
| GitHub Spec Kit ↗ | Solo spec-first. Sin orquestación de agentes. |
| Kiro ↗ | IDE cerrado. Sin multi-agente. |
| Tessl ↗ | Beta. 1:1 spec-to-file. Sin quality gates. |
| SPARC ↗ | Solo planning. Sin ejecución ni verificación. |
| Claude-Flow ↗ | Orquestación genérica. Sin pipeline SDD. |
| OpenSpec ↗ | Ligero pero sin testing ni evidencia. |
| cc-sdd ↗ | Composable traits pero acoplado a Spec Kit. |
| BMAD ↗ | Complejo. No es SDD puro. |
Where SpecBox Fits
| Capability | Spec Kit | Kiro | Tessl | SpecBox |
|---|---|---|---|---|
| Spec generation (PRD) | ✅ | ✅ | ✅ | ✅ |
| Plan generation | ✅ | ✅ | — | ✅ |
| Multi-agent orchestration | — | — | — | ✅ |
| Autonomous implementation | — | 🔶 | 🔶 | ✅ |
| BDD/Gherkin quality gates | — | — | — | ✅ |
| Self-healing protocol | — | — | — | ✅ |
| Evidence per feature | — | — | — | ✅ |
| E2E con Playwright | — | — | — | ✅ |
| Project management integrado | — | — | — | ✅ |
| MCP tools nativos | — | — | — | ✅ |
| Quality Ratchet (85%+ coverage) | — | — | — | ✅ |
| Pipeline blocking hooks | — | 🔶 | — | ✅ |
| Multi-stack support | — | — | — | ✅ |
VEG — Visual Experience Generation
VEG — Visual Experience Generation
SpecBox-exclusive system that generates intentional visual decisions (images, animations, design directives) tailored to the product's audience. 3 operating modes, 6 audience archetypes, 3 generation pillars.
3 Modes
A single VEG for homogeneous audiences.
Visual variants per user profile.
Personalized per ICP with rational and emotional JTBD.
3 Pillars
Generation via MCP (Canva, Freepik). Type, mood, palette, per-section prompts.
Animation catalog by level. flutter_animate / Framer Motion.
Stitch directives: density, whitespace, typography, CTA, shadows.