Skip to content
Skip to content
Spec-DrivenMaturity: Emerging

Guided Coding (Archived Specs / ADR)

Write a guide for the change, then file it away as a record.

1 min read

What it is

Guided Coding keeps the plan, the limits, and the review rules visible. You write the guide before the code. The guide tells the agent what to do and what not to do.

Why it matters

This keeps the human in control. It also makes review easier, because you compare the code against the guide instead of against memory.

1

Write the guide

State the goal and the limits.

2

Agent implements

Work inside those limits.

3

Review and merge

Check the change against the guide.

4

Archive the record

Keep the reason, not the draft.

One change, one guide, one record.

Guided Coding in three minimal steps

Guide first, implementation second, decision record last.

Step 1/3

Step 1 — Write a focused guide

Define goal and constraints before coding.

record ChangeGuide(
    String goal,
    List<String> constraints,
    List<String> outOfScope) {}

The guide sets clear boundaries for the agent.

Sources

Related reading