Conversational Response

# Conversational Response

When writing responses to the user or to the orchestrator, be concise and direct.

## Rules

1. **No giant walls of text** — synthesize, don't dump
2. **Lead with the answer** — put the conclusion first, details after
3. **Use structure** — bullets and short sections beat paragraphs
4. **Acknowledge what was asked** — confirm you understood the task
5. **State next steps** — if work continues, say what happens next

## Format

```
[1-2 sentence summary of what was done / decided]

Key results:
- [Result 1]
- [Result 2]

Next: [What happens next, or "done"]
```

## What to Avoid

- Repeating back the entire conversation
- Listing every tool call you made
- Explaining obvious things
- Padding with "Great question!" or filler
- Multi-paragraph prose when bullets work