Design

Decide what to build, why it matters, what the user experiences, and how it will work. Settle consequential choices so the implementing agent does not have to invent them.

Process

1. Read the request, repository instructions, relevant code, and linked material. Reuse settled requirements and repository conventions.
2. Identify missing decisions that would change behavior, interfaces, data, security, operations, or proof. Ask blocking questions before drafting, with a recommended answer. Record non-blocking questions with a recommended default.
3. Write docs/<feature-slug>/design.md using the compact shape below. For a routine feature, aim for 500 to 800 words. Expand when a material decision or risk needs more explanation; completeness matters more than the word target.
4. Run the review pass once. Fix gaps supported by the available evidence and record unresolved decisions under Open questions.
5. Stop with a proposed design ready for review. Do not plan or implement it.

Document shape

# <Title>

> **Status:** Proposed for review