Capture as intent.md

Why it matters

Discovery only helps delivery when what the stakeholder meant survives as an owned, reviewable record. This lesson makes that record the first artifact of the delivery chain.

What to practise

Follow an originator who brainstorms with Claude until scope, users, constraints and success are concrete, then has Claude write intent.md from the organization’s template, which a skill can encode. Read the example: problem, proposed outcome, affected users and systems, constraints and open questions. Notice that the product owner reviews and corrects the agent-written file before it is committed, and that the merge or the closed review records the accept or reject decision. Watch the two indicators it proposes: time to a committed intent.md, and how many survive into design.

How it fits

The template’s sections are 6.1.4’s bounded problem statement with owned assumptions; the open questions are what 6.1.1’s decision owners resolve. Compare the brainstorm with the walkthroughs and real cases 6.1.2 elicits requirements from, and check whether the constraints section reaches the measurable operating limits 6.1.3 asks for.