From Writing Code to Writing Specs: Spec-Driven Development and the Rise of Agents

A quiet but large shift is underway in software development: developers write fewer lines of code by hand and more specifications describing 'what they want', while agents take on the implementation.

The market is changing hands fast

• Codex adoption grew ~5×, from 3% in January 2026 to 16% in May–July; awareness rose from 27% to 65%.
• GitHub Copilot declined from 29% a year ago to 21%; still the best-known tool with 79% mind share.
• Google reports 25% of its code is AI-assisted, with ~10% velocity gains.

Maturation: trust and governance

Tools are no longer 'novelty experiments' but production-grade workflows. MDM policies, org-wide tool restrictions and session auditing appear consistently across Copilot, Claude and Pi — enterprise adoption pressure has pushed security and auditing to the front.

Spec-driven development

The new model forms around focused working sessions: the developer writes a clear spec, the agent implements, a human reviews. That boosts speed while repositioning responsibility: quality is set not by the code itself but by the clarity of the spec and the verification layer.

The remot angle

remot brings coding agents under orchestration discipline too: it routes which agent uses which model, measures call cost and trace, and enforces enterprise security and audit policy. That way 'agents that write code' become a measurable, auditable pipeline rather than an uncontrolled force.