Confirm final stack selection and document trade-offs. Use after stack-evaluation presents candidates, when user is ready to choose a stack.
Confirm the user's final stack selection, document accepted trade-offs, and capture decision notes.
Present top recommendations and ask user to confirm:
Which stack would you like to proceed with?
<candidate> (Score: X.X)<candidate> (Score: X.X)<candidate>Present known trade-offs for selected stack:
| Category | Trade-off | Impact |
|---|---|---|
| Cost | ... | low/medium/high |
| Ops Overhead | ... | low/medium/high |
| Vendor Lock-in | ... | low/medium/high |
| Learning Curve | ... | low/medium/high |
Do you accept these trade-offs?
Ask for additional context:
Confirm local development approach works for the team.
selected_stack:
stack_id: "<unique id>"
name: "<name>"
selected_at: "<ISO timestamp>"
components:
frontend:
technology: "<tech>"
hosting: "<hosting>"
backend:
technology: "<tech>"
hosting: "<hosting>"
database:
technology: "<tech>"
hosting: "<managed|self-hosted>"
auth:
provider: "<provider>"
async:
technology: "<tech>"
storage:
technology: "<tech>"
local_dev:
approach: "<docker-compose|local-k8s|hybrid|aspire>"
time_to_first_run: "<estimate>"
evaluation_summary:
weighted_score: <score>
rank: <rank>
strongest_areas: []
weakest_areas: []
accepted_tradeoffs:
- category: "<category>"
description: "<trade-off>"
mitigation: "<how to mitigate>"
decision_notes:
rationale: "<why chosen>"
concerns: []
timeline_considerations: "<notes>"
references:
architecture_brief_id: "<ref>"
evaluation_id: "<ref>"
Present final confirmation:
Stack: <name>
Components:
<tech> on <hosting><tech> on <hosting><tech> (<hosting>)<provider>Local Development: <approach> (Est. <time> to first run)
Accepted Trade-offs:
<trade-off 1><trade-off 2>Proceed to implementation-plan skill to create execution-ready implementation plan.