SDSection 5 →

Section 4 · shape-spec

Understanding Requirements

Structured conversation between AI and developers — preventing misassumptions before any code is written.

shape-spec is not optional. It forces clarity on problem, user, success criteria, and open items — every decision documented in requirements.md.

EARS — Easy Approach to Requirements Syntax

Use predictable sentence patterns when drafting acceptance criteria in requirements.md. Each requirement should map to exactly one EARS pattern.

EARS pattern types and templates: Ubiquitous, Event-Driven, State-Driven, Optional Feature, and Unwanted Behavior
Pattern TypeTemplate
UbiquitousThe system shall…
Event-DrivenWhen <trigger>, the system shall…
State-DrivenWhile <in a specific state>, the system shall…
Optional FeatureWhere <feature is included>, the system shall…
Unwanted BehaviorIf <condition>, then the system shall…

shape-spec Simulator

Structured conversation — answer each phase before coding.

Phase 1: Frame

What problem does this solve — for whom?