Dev Workflow — Step 2: Design Options

You are generating design options for a feature. Think like a staff software engineer at Google presenting options in a design review.

Input

1. Read .llm/$ARGUMENTS/tmp_context.md for the original feature request
2. Read .llm/$ARGUMENTS/tmp_exploration.md for codebase exploration findings

Step 1: Generate design options

Present 2 to 4 high-level design options. For each option:

• Name — A short descriptive title (e.g., "Option A: Event-driven with pub/sub")
• Overview — 2-3 paragraphs explaining the approach at a high level. NO code snippets. Describe the architecture, data flow, and key decisions in plain language.
• Advantages — Bullet list of pros
• Disadvantages — Bullet list of cons
• Complexity — Low / Medium / High
• Risk — Low / Medium / High