Architecture Decision
Agent proposes approaches, team picks one async
Architecture Decision
Your agent researches options and presents them as a structured decision. The team reviews async.
The prompt
"Analyze our options for the real-time notification system. Compare WebSockets, SSE, and polling. Publish a decision document with a vote on the approach."
Questions that drive decisions
[
{ "id": "approach", "type": "choice", "text": "Which approach should we use?", "options": ["WebSockets", "Server-Sent Events", "Long polling"] },
{ "id": "concerns", "type": "multi", "text": "What concerns apply?", "options": ["Complexity", "Scalability", "Browser support", "Cost", "Latency"] },
{ "id": "timeline", "type": "choice", "text": "When should we start?", "options": ["This sprint", "Next sprint", "After Q2"] },
{ "id": "notes", "type": "text", "text": "Additional context?" }
]Why async works
- Team members review on their own schedule
- No meeting needed for straightforward decisions
- Each person's vote is recorded independently
- Agent can aggregate results: "3 voted WebSockets, 1 voted SSE, concerns: complexity (2), cost (3)"