Conductor turns specs into agent artifacts

Google's Conductor update frames spec-driven development as persistent Markdown artifacts such as specs and plans that can travel across agent CLIs. Why it matters: Agent coding becomes easier to audit when requirements, plans, and execution notes survive outside a chat transcript and can be reviewed, versioned, or reused by different tools.

Try this: Before starting an agent build, create a short spec and plan file, then require the agent to update those artifacts when scope, assumptions, or implementation steps change.