SDD tooling is not the battleground — the enterprise platform surrounding it is.
Standalone IDE with built-in SDD workflow
End-to-end enterprise development platform with SDD
The SDD workflow layer is at competitive parity (4:4 tie). The 1.40-point enterprise readiness gap reflects platform depth, not SDD quality. Kiro competes on the SDD workflow layer; GitHub + Microsoft competes on the entire software development lifecycle — security, governance, compliance, multi-cloud, observability, and enterprise data.
Click any chapter to dive into the full analysis.
What SDD is, why it emerged from "vibe coding," market sizing ($3.5-7B), adoption signals, and the Fowler maturity framework (spec-first, spec-anchored, spec-as-source).
The 5-layer GitHub + Microsoft enterprise stack: Security (GHAS, Defender, Firewall), Governance (Purview, Content Safety), Agent Orchestration (Foundry, GitHub Models), DevEx (Spec Kit, Copilot SDK), Enterprise Data (Work IQ, M365).
Side-by-side analysis: Kiro (EARS notation, PBT, agent hooks) vs. Spec Kit (constitution, gated phases, 25+ agents). Plus BMAD-METHOD, Tessl, SPARC, OpenSpec positioning.
Two capability matrices (9 SDD + 14 Platform capabilities), color-coded edge badges, and a Gartner-style positioning quadrant mapping 6 vendors across SDD depth vs. platform breadth.
9-criterion weighted scoring (vendor independence, security, scalability, pricing...), explicit calculation (2.85 vs. 4.25), radar chart visualization, and gap interpretation.
Full SWOT grids for both approaches, plus tailored recommendations for AWS-invested, GitHub/MS-invested, multi-cloud, and SDD-new organizations. 4-phase adoption roadmap.
2026-2028 predictions: platform wins over IDE, model freedom as non-negotiable, SDD on the hype cycle, MDD historical parallel. Complete reference list (39 sources).
SDD Market Positioning Quadrant — March 2026. Bubble size represents relative platform breadth and ecosystem maturity.