Adopt the four-phase spec-driven loop (Specify → Plan → Tasks → Implement) to stop agent intent-drift

BCMS·medium signal

Spec-driven development makes a version-controlled, executable specification — not the code — the single source of truth, directly countering vibe-coding's failure mode where agents produce plausible code that drifts from intent and hallucinates APIs. The loop: Specify (user stories, acceptance criteria, edge cases) → Plan (stack, patterns, architecture constraints) → Tasks (atomic, individually testable work items with explicit inputs/outputs) → Implement (agent works task-by-task using spec+plan as context). Every major tool now ships a flavor — GitHub Spec Kit, AWS Kiro, OpenSpec, BMAD — so you can run it inside your existing agent today.