Delineate

Describe the system from the functional side: what it is for, who it serves, the domain contexts it divides into, the capabilities it offers, the requirements imposed on it from outside the code, and the words everyone uses for all of that. Technology, structure, and design are out of scope; name one only when a requirement imposes it, and record it as that requirement.

Take one branch:

• Outline: build or revise the system's functional picture. Run every section below.
• Term: one word is fuzzy or disputed mid-task. Run only "Challenge terms" and "Write it down" for that word, then return to the task.

Gather

Read what exists before asking anything: README.md, AGENTS.md, and the documents AGENTS.md names (the domain outline, the requirements, the glossary, existing capability specifications), and the code's entry points and domain types. A kind of document AGENTS.md does not name does not exist yet; when you notice a likely one it does not name, mention it in your report instead of using it. Draft every section of the outline from that evidence, marking each claim as stated by a document or inferred from the code.

Outline

Settle the draft with the user through the interview method, recommending an answer from the evidence for each question: