Spec-driven development with AI

Let the agents build after you write the spec

A prompt describes a wish; a spec describes done. This handbook shows how to write specs AI agents can follow. Your team approves the plan before any code is written and reviews a tested pull request at the end.

spec.md · OPS-341 CSV exportWriting the spec…

ACCEPTANCE CRITERIA1.Export the filtered grid as CSV2.Same 5 columns as the screen3.Up to 50,000 rows4.Error message when the export fails

Waiting for spec approvalCHECKPOINT 1

Developer builds in a sandboxTests: 4 of 4 criteria passReviewer and Security check

✓PR #2202 ready for reviewnext: review · merge

SPEC FIRST, THEN CODE

INSIDE THE HANDBOOK01What spec-driven development is, and why AI needs it02How context decay and hidden decisions cause drift03The step-by-step workflow, from problem to merged change04Templates for specs, plans, and task breakdowns05How developers, leads, and architects each use it

Built by Syncfusion, serving 47,000+ organizations.25+ years of developer tools, now reimagined for the agent-first era.

47,000+Syncfusion customers

1,600+Syncfusion UI components

25+Years of Syncfusion developer tools

Syncfusion component licensing is separate.

Look inside

Preview the handbook’s five chapters

Free PDF · 5 chapters

BOLDCREATE HANDBOOKSpec-driven development01What spec-driven development is, and why AI needs it

YOU WILL LEARNA prompt describes a wish; a spec describes doneAmbiguity is where agents improviseWhy AI makes specs more valuable, not less

FIGURE 01

Without itWith it“Add export”CSV, 5 columns, max 50k rows“Make it fast”p95 under 300 ms“Handle errors”3 named error states

Chapter 01 of 05

From reading to running

Put the handbook into practice with BoldCreate

Written for

DevelopersTech leadsEngineering managersArchitects

1Cloud AgentDescribe the goalType it in plain language. The Planner drafts the spec from your codebase.› spec: OPS-341 · 5 criteria

2Auto modeApprove the specYour first checkpoint. Agents then build and test in an isolated sandbox.› spec: OPS-341 · approved

3Cloud AgentReview test results before mergingThe PR includes test results for each criterion. Your team reviews and merges.› PR #2202 · 5 of 5 criteria tested

The spec-first flow

Your team approves the spec, reviews the pull request, and merges

The handbook explains why a written spec keeps AI agents on track. In BoldCreate it is also the first of three checkpoints, so people decide what gets built and what gets merged.

1Describe the taskYouPlain language, a ticket, or pasted notes. The Planner reads your codebase and drafts the spec.
2Approve the specCHECKPOINTYour teamGoal, scope, non-goals, and acceptance criteria. Nothing is built until you approve it.
3Build and test in a sandboxDeveloper, DesignerAgents follow the approved spec in an isolated sandbox for this task and write tests for each criterion.
4Review the pull requestCHECKPOINTYour teamThe PR carries the available evidence: test results, Reviewer and Security findings, and the task cost.
5MergeCHECKPOINTYour teamYour team merges when it is satisfied. The spec stays with the change for the next person.

Spec-driven vs. prompt-driven

Compare spec-driven and prompt-driven development

Where requirements are recordedSpec: In a written spec the team approvedPrompt: In a chat history that grows and drifts

When decisions are madeSpec: Before any code is writtenPrompt: While the code is being generated

When requirements changeSpec: Update the spec, then the code followsPrompt: Re-prompt and hope earlier choices hold

How the result is checkedSpec: A test for each acceptance criterionPrompt: Read the diff and guess what was meant

When to use each approachSpec: Features, fixes, and changes that need to lastPrompt: Quick experiments and throwaway prototypes

Frequently asked questions

What is spec-driven development?

Spec-driven development means writing down what “done” looks like before any code is written: the goal, the scope, what is out of scope, and the acceptance criteria. AI agents then build against that spec instead of guessing from a one-line prompt.

What’s inside the spec-driven development handbook?

It’s a free PDF with five chapters. It explains why AI needs specs and how context decay and hidden decisions cause drift. It then gives a step-by-step workflow from problem to merged change, templates for specs, plans, and task breakdowns, and how developers, leads, and architects each use it.

How does BoldCreate use specs?

You describe a task and the Planner drafts a spec from your codebase. Your team approves it before anything is built. Agents then build and test in an isolated sandbox, and the pull request comes back for your team to review and merge.

Where do people stay in control?

At three checkpoints: you approve the spec, you review the pull request with its test results, review findings, and task cost, and your team decides when to merge.

What if requirements change mid-task?

Update the spec first. The agents work from the updated spec, so the spec stays the source of truth instead of a long chat history.