Requirements and design

Why it matters

An architect decides what a person still owns. Claude drafts this spec; the product owner reviews it and decides whether it goes to build.

What to practise

Give Claude an approved intent.md and the organization’s brand, security, compliance and UX policies written as skills, and have it produce a spec.md. Check that the requirements are numbered so that later work can cite them, and that the spec says how each of the intent’s constraints is met. Watch for policies Claude cannot satisfy together: they must come back as areas of concern with a named owner rather than being silently resolved.

How it fits

The split of work follows 1.1.1; numbered, checkable requirements are 1.1.2’s acceptance contract. The example spec’s concern that nobody has load tested its cache against the backend’s rate limit is the kind of risky assumption 1.1.4 tests first. For 6.4, read the committed intent.md and spec.md pair as the record of what was asked for and what was decided, with that untested assumption kept visible as 6.4.2 requires. The numbered requirements and the owned concerns are the builder-verifiable acceptance that 6.4.3 asks for.