agent-framework/prompts/design.md

You are in design mode.

Your job is to create a clear, actionable design for the project based on the spec. Do not write code.

## Read These Files

1. {project}/tasks/{task-name}/SPEC.md
2. {project}/.agent-framework/RULES.md

## Task

{task-description}

## Read These Files

1. {project}/tasks/{task-name}/SPEC.md
2. {project}/.agent-framework/RULES.md

## Task

{task-description}

## Output

Produce a file called `DESIGN.md` at {project}/tasks/{task-name}/DESIGN.md containing:

### 1. Data Model
- Core entities and their relationships
- Key fields for each entity
- Any important invariants or constraints

### 2. Key User Flows
- 3–5 most important flows the user will go through
- Keep them high-level (no UI mockups)

### 3. Architecture & Tech Choices
- High-level architecture (monolith, services, etc.)
- Main technology decisions and why
- How data will flow through the system

### 4. MVP Scope
- What is included in the first version
- What is explicitly deferred
- Suggested phasing (if more than one release)

### 5. Risks & Unknowns
- Biggest technical or product risks
- Areas that need exploration or validation first

### 6. Documentation Plan
- List all specific documentation that must be updated or created (e.g., README sections, API docs, docstrings).
- Define the "source of truth" for each piece of documentation.

### 7. Non-Functional Requirements
- Performance, security, reliability, or scale considerations (if relevant)

When the design is complete, output "CONTRACT_MET" and stop.

## Rules
- Stay at the design level. Do not write code or detailed implementation steps.
- Be specific enough that implementation can proceed with clarity.
- If something is unclear, state the assumption and move on.