Project Brain

Use gh to read the project's separate Git-backed knowledge base. Treat the brain as evidence: cite repository paths and the commit inspected, distinguish documented facts from inference, and say when the repository does not answer the question.

Mandatory preflight

Before planning, answering, reviewing, diagnosing, documenting, or changing files in a Git worktree:

1. Resolve the current worktree root with git rev-parse --show-toplevel.
2. Check that root for .project-brain.json.
3. If the file exists, invoke this workflow and consult the brain before substantive reasoning or action. The marker is an unconditional instruction; do not wait for the user to mention Project Brain and do not decide that consultation is unnecessary.
4. Read enough relevant brain material to ground the task. At minimum, read agent-guide.md when it exists, then discover and read the sources relevant to the request.
5. If the brain cannot be reached, report the specific blocker. Do not silently continue with ungrounded assumptions.

The Project Brain is a separate repository identified by the marker. Do not expect it inside the active project, add it as a child directory, or clone it into the active worktree.

Resolve the brain

1. Read .project-brain.json from the active worktree root. Accept this shape: