Repository brief

Capture the facts that change implementation decisions, with sources another agent can reopen. A brief is maintained evidence, never an authority above user or repository instructions.

Phase 1: Bound the question

• Identify the task or subsystem and the next consumer. Read agent instruction files (for example AGENTS.md), manifests, lockfiles, lint/format config, CI and representative nearby code. Trace one real flow before describing architecture. Use flow-onboard first if a broad tour is needed; do not scan the whole repository for a narrow change.
• Write to the user's knowledge location, else .plans/context/<topic>.md. Preserve tracked or ignored status and say when an ignored file is local-only. Do not change global instructions, ignore rules or installed skills as a side effect.

Phase 2: Separate fact from inference

Cite a path plus symbol or line range at the recorded revision for every load-bearing claim; add command output for operational claims. Capture: