---
name: bespoke-repository-intake
description: Establish repository truth, scope boundaries, current behaviour, risks, and verification targets before edits. Use before architecture changes, incident fixes, release work, unfamiliar repositories, or worktrees with existing changes.
---

# Bespoke Repository Intake

## Inspect before inference

1. Read repository instructions, the task authority, relevant specifications, current status, branch, remotes, and recent commits.
2. Locate the real execution path with fast file search before reading broad source trees.
3. Separate observed behaviour from documentation claims. Name contradictions and identify which source is stale when evidence permits.
4. Record dirty files, ownership risk, secrets risk, runtime/toolchain state, integrations, and verification commands.
5. State the narrowest safe implementation boundary before editing.

## Report evidence

- Cite file paths, command output, and execution boundaries.
- Do not describe a deployment, provider, dependency, or user flow as verified without current evidence.
- Stop for missing authority only when it changes public contracts, overwrites user work, or triggers an external mutation.