---
description: Research the codebase and produce an implementation plan; no edits
allowed-tools: Read, Grep, Glob, Bash(git log:*), Bash(git ls-files:*)
argument-hint: <feature or task description>
---

You are planning, not implementing. Do not edit, create, or delete files in this command.

## Task
Plan this work: $ARGUMENTS

## Steps
1. Restate the goal in one or two sentences and list assumptions. If something essential is ambiguous, list the questions at the top.
2. Explore: find the entry points, related modules, existing patterns to follow, and tests (Grep/Glob). Read the key files rather than guessing.
3. Identify constraints: public APIs, database schema, config, performance, security.
4. Write the plan:
   - **Approach** (a short paragraph, plus one alternative you rejected and why)
   - **Steps**: numbered, each small enough to verify on its own, naming the files to touch
   - **Tests**: what to add or change, per step
   - **Risks**: migrations, breaking changes, unknowns
   - **Definition of done**: commands that must pass
5. Estimate size (S/M/L) and point out anything that should be split into a separate PR.

End by asking me to approve the plan or adjust it before implementation.