Requirements and design with AI
Mid / SeniorUsing LLMs to refine requirements, explore design options and record decisions without outsourcing the judgment.
Created 19 October 2026
7 concepts · detail hidden
01Glossary — terms used in this page
#c-glossary-terms-used-in-this-page- ADR (Architecture Decision Record) — a short document capturing a design decision, its context, alternatives and consequences.
- Acceptance criteria — testable conditions that define when a story is done.
- Spec-driven development — writing a precise specification first and having the AI implement against it.
- Non-functional requirements — qualities such as latency, security, availability and compliance, as opposed to features.
02Turning vague requests into a requirements brief
#c-turning-vague-requests-into-a-requirements-briefAn LLM is good at structuring: extract stakeholders, goals, assumptions, open questions and acceptance criteria from meeting notes or a one-line ask. The valuable output is the list of open questions, not the polished prose. Have the model separate stated facts from assumed ones so assumptions get confirmed by a person.
03Finding gaps and contradictions in a specification
#c-finding-gaps-and-contradictions-in-a-specificationPrompt the model to act as a reviewer: list ambiguous terms, missing error and edge cases, conflicting requirements, and unstated non-functional needs. It is cheap to run repeatedly and catches problems before any code exists, where they cost least.
04Design exploration and trade-off analysis
#c-design-exploration-and-trade-off-analysisAsk for two or three architecture options with trade-offs against your stated constraints (team size, existing stack, scale, budget). Without constraints, answers are generic. Use the model to argue against your preferred option, and verify claims about specific products against current documentation.
05Drafting ADRs and diagrams
#c-drafting-adrs-and-diagramsModels draft ADRs, sequence diagrams and Mermaid/PlantUML source quickly from a discussion transcript. The human supplies the decision and rationale; the model supplies the structure. Store ADRs in the repo so future agents and humans can read them as context.
06Spec-driven development with an agent
#c-spec-driven-development-with-an-agentWrite a spec (behavior, interfaces, constraints, acceptance criteria), have the agent propose a plan, review the plan, then implement in small steps. Reviewing a plan is far cheaper than reviewing a finished wrong implementation. The spec doubles as the source for tests.
07Limits — what AI cannot decide for you
#c-limits-what-ai-cannot-decide-for-youProduct priorities, risk appetite, organisational constraints and accountability stay human. The model has no stake in the outcome and can make any option sound reasonable, so a decision made only because “the AI recommended it” is a smell.