prd — the strategic layer of a product

It interviews the operator and produces the strategic definition of a product: vision, problem, users, scope, competitors, opportunities, open questions and glossary. It is the entry door to the method — out of this layer come the specs.

It always writes into the context/ of the loaded product node of the brain, never into the body repo. The repo declared in repo: of the node's head is the body: specs, technical decisions, as-built. The strategic layer lives in the head, not in the body.

The interview applies pressure with the method of .claude/skills/grill/SKILL.md#method: it is cited by that heading, never copied. Any change to the method happens there, once.

The files it produces

They go into context/ of the loaded product node. If the node has no context/ yet, it is born with README.md first and the rest as the interview gets completed.