The rise of AI coding assistants—Cursor, Claude, GitHub Copilot—has shifted the main challenge from writing code to communicating intent. When engineers give an LLM a vague feature description or unstructured prompt, the model often drifts. It invents edge cases, guesses API endpoints, or generates lots of valid code that solves the wrong problem. To keep […]
Read More →Spec-driven development treats a structured specification—not the codebase—as the system of record. This post maps who does what when you work that way: from turning product intent into an agent-readable spec, through API contracts and UI rules, to validation that implementation still matches what you wrote down. Table of contents Overview Spec-driven development (SDD) is […]
Read More →In OpenSpec, the standard spec format is a structured Markdown document that defines exactly what a system should do through requirements and how that behavior is verified through scenarios. 1. Core Specification Structure (spec.md) The “Source of Truth” file (located in openspec/specs/<domain>/spec.md) follows a specific hierarchy: 2. The Scenario Format (GIVEN/WHEN/THEN) Scenarios are the most critical […]
Read More →