Tag
3 posts tagged.
I shipped the same feature twice, once in Kiro and once in Claude Code. The code converged; the workflow did not. How I route between spec-driven and terminal-native in 2026.
Quick answer (2026): I ran the same feature through GitHub Spec Kit, Kiro, and a plain plan.md in Claude Code to see which spec-driven setup actually earns its place. Spec Kit wins for writing shared project rules, Kiro wins for killing spec-and-code drift, and a hand-written plan.md wins on setup cost. The plain plan.md is the one I kept.
I ran spec-driven development for a month on a live B2B product. An honest 2026 field log: where the spec earned its overhead, where it was pure ceremony, and the six-heading spec that survived.
