Survey Patterns

Search the codebase for analogous features and reusable building blocks before planning a change. Returns structured findings. Does not write code or plans.

Step 1: Identify the Task

Determine what the change is about:

• If a task description was passed in, use it
• Otherwise, derive it from conversation context (the user's latest request)

State the task back in one sentence to confirm scope before searching.

Step 2: Spawn Pattern Survey Subagent

Spawn a single subagent in the foreground (model: "opus", no name). Its prompt must direct it to treat the shared working tree and its git index as read-only and to survey by reading and reasoning. HEAD stays where it is: read other refs with git show <ref>:<path> rather than git checkout or git switch. The subagent's prompt must include:

1. The confirmed task description from Step 1
2. An instruction to read references/pattern-surveyor.md for survey guidelines, categories, and output format before searching