Spec-Driven Development
Spec-driven development means giving AI coding agents a structured, durable specification to build against instead of ad-hoc prompts. Harmonic Composition provides that spec layer through Beats and six quality gates.
Spec-Driven Development
Spec-driven development is the practice of giving AI coding agents a structured, durable specification to build against — rather than ad-hoc prompts or disposable tickets. In Harmonic Composition, that specification layer is made of Beats (durable capability definitions) governed by six quality gates, so the spec is both rigorous and built to last.
Spec-driven development (also written "spec driven development") is an approach where a clear, structured specification — not a prompt typed in the moment — is the source of truth an agent or team builds against. The spec defines what the system must do and how "good" is judged, so execution can be verified against intent. The open question every spec-driven approach must answer is: what makes a spec good, and how is that enforced?
Why spec-driven development matters for AI coding agents
AI coding agents execute against whatever specification they are given. A vague prompt produces fast, confident, wrong work; a precise, durable spec produces work that converges on intent. As agents take over more execution, the quality of the spec becomes the dominant variable in whether the output is right.
The difficulty is that most "specs" in practice are ephemeral: a prompt, a ticket, a paragraph in a doc. They are not durable, not evaluated for quality, and not connected to the system's destination. Spec-driven development only delivers on its promise when the spec itself is a first-class, quality-gated artifact.
The spec layer: Beats + quality gates
Harmonic Composition treats the specification as a durable artifact, not a throwaway instruction:
- Beats are the spec units — durable, outcome-oriented capability definitions that persist and evolve through Revisions rather than closing like tickets.
- Quality gates are how the spec is enforced. Every Beat must satisfy six dimensions — Distinctive, Harmonious, Substantial, Durable, Clear, and Strategically Aligned — before work begins. An LLM evaluates all six in seconds and returns a scorecard with remediation steps.
Together these answer the question other spec-driven approaches leave open: a Beat is the spec, and the quality gates define what makes it good. An agent building against a quality-gated Beat is working from a specification that has already been checked for clarity, coherence, and fit.
How it compares to writing specs by hand
Traditional specifications are written once, reviewed in a meeting, and then drift out of date the moment implementation begins. A spec-driven workflow built on Beats is different in three ways:
The spec persists and evolves with the capability instead of being archived after the first build.
Quality gates check the spec against six explicit dimensions before any code is written.
Every spec is checked against the Coda, so it advances where the system is actually headed.
Spec-driven development works when the spec is a durable, quality-gated artifact an agent can reason about — not a prompt that disappears after one use.
Frequently asked questions
- What is spec-driven development?
Spec-driven development is an approach where a clear, structured specification — not an ad-hoc prompt — is the source of truth a team or AI coding agent builds against. The spec defines what the system must do and how quality is judged, so execution can be verified against intent. Its central question is what makes a spec good and how that is enforced.
- How does spec-driven development work with AI coding agents?
AI coding agents execute against whatever specification they are given, so the quality of the spec is the dominant variable in whether the output is correct. Spec-driven development gives agents a precise, durable specification instead of an ephemeral prompt. In Harmonic Composition, that spec is a Beat — a durable capability definition — that has passed six quality gates before any code is written.
- How does spec-driven development scale without specs going stale?
Specs go stale when they are written once and archived. Harmonic Composition keeps the spec durable: Beats persist and evolve through Revisions rather than closing like tickets, quality gates re-evaluate them when they change, and every Beat is checked against the Coda (the destination) so the spec stays connected to where the system is headed. The spec evolves with the capability instead of drifting out of date.
Software Development Methodology
A software development methodology is the system of principles, practices, and primitives a team uses to plan, build, and evolve software. Harmonic Methods is a modern methodology built for the AI era, where agents execute and intent must be explicit.
Context Engineering
Context engineering is the discipline of structuring the reasoning behind software — decisions, constraints, assumptions — so people and AI coding agents can act on it. In Harmonic Methods that discipline is made concrete through Notes.