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.
Guided Coding in a repeatable 3-step loop
Natural-language spec, spec refactor, implementation — then repeat.
Step 1/3
Step 1 — Write a natural-language specification
Capture intent in plain language before touching implementation.
String specV1 = """
Add a transfer endpoint.
Keep package boundaries unchanged.
Do not change the database schema.
Return 200 on valid transfer requests.
""";The first draft states intent in human language.
loops to step 1