Consult Descriptions

docs/product/ and docs/architecture/ hold the project's descriptions of itself as it stands now. A product behavior document covers one capability and states what the product does today, in the shape <skill_path>/references/formats/product-behavior.md fixes; an architecture description covers one module and states how the system is structured today, in the shape <skill_path>/references/formats/architecture-description.md fixes. Both are living: they describe the present, and they change only when a thread's delta documents land.

List what exists

Neither folder carries an index. Print every document's path with its headings, without loading a single body:

find docs/product docs/architecture -maxdepth 1 -name '*.md' 2>/dev/null | sort | while read -r f; do printf '%s\n' "$f"; grep -n '^#\{1,2\} ' "$f" | sed 's/^/  /'; done

A folder that does not exist yet prints nothing: the project layer is created lazily, and an absent folder means nothing of that kind has been described.

Open what the work touches

From the listing, open the product behavior of every capability the work touches and the architecture description of every module it touches, and read each in full. A description is admitted only where the code does not already make the point obvious, so what you find there is what reading the code would not have told you.

How a description is cited and read