Map the repo before you change it

Use a map when the repo is unfamiliar

A Brief map is source-grounded orientation, not a giant repository summary. It should return only the paths, relationships, rules, and checks that help with the current task.

• Use it before a cross-cutting feature, refactor, or unfamiliar bug.
• Use it when the agent is about to invent a helper or component.
• Skip a full map for an obvious, isolated one-line change.

Ask for the smallest useful map

Use Brief to map the part of this repo relevant to <task>. Find the entry points, data flow, applicable team rules, closest proven implementation, owners, and focused tests. Cite every recommendation and keep the packet compact. Don't edit yet.

Turn the map into a mission

Use this map to plan the smallest mission that produces a user-visible result. Name what is in scope, what is not, the reuse path, validation, approvals, and the conditions that should stop the work.