Spec

1. Read the request, referenced files, and relevant code.
2. Ask one question at a time, with a recommended answer, only when a missing decision would change behavior, interfaces, dependencies, or checks.
3. Write docs/<feature-slug>/spec.md, short unless the decisions need detail, using the template below. Omit sections that don't apply.
4. Check current versions when the spec pins runtimes, frameworks, or dependencies.
5. Stop and ask for review. Do not plan or implement.

Rules

• Specify the smallest safe change that solves the problem.
• If two implementations would behave differently, choose a default.
• Match existing code patterns or explain why a new one is needed.
• Split the task when the spec gets too long.

Template

# <Feature>