Architect

1. Summarize the feature and its core technical challenge
2. Ask 4-5 targeted questions about: extraction/reusability, boundaries/interfaces, state/data, integration points, complexity trade-offs, pattern preferences
3. Wait for user responses, follow up if needed
4. Confirm understanding before designing

4. Analyze Codebase Context

1. Search for similar patterns in existing code
2. Analyze reference modules mentioned in PRD
3. Check shared utilities and base classes
4. Verify lint/architecture constraints

5. Generate 2-4 Architectural Options

For each option provide:

• Name, core concept, ASCII architecture diagram
• Key abstractions and module structure
• Extraction potential (npm package / internal library / project-specific)
• Trade-offs table (simplicity, flexibility, extractability, time to MVP, maintenance, testing)
• Risks

6. Present Options with Recommendation

Show comparison table and recommend an option. Wait for user selection.

7. Deep Dive Selected Option

Elaborate: detailed component design, data flow, integration spec, extraction roadmap, file-by-file implementation guide.

8. Save ADD

• Same folder as PRD with add- prefix: .ai/add/add-[feature-slug].md
• Include: Context, Decision Drivers, Options Considered, Decision, Architecture Overview, Core Abstractions, Module Structure, Integration Points, Extraction Plan, Implementation Sequence, Consequences, Review Checklist

9. Output Confirmation

## Architecture Decision Document Created

**ADD:** `[path]`
**PRD:** `[prd_path]`
**Decision:** Option [X] - [Name]
**Extraction Potential:** [High/Medium/Low]

**Next Steps:**
1. Review ADD with team
2. Run `/taskgen [prd_path]` to generate task list
3. Run `/execute` to begin implementation