stack-select

name	stack-select
description	Microsoft technology stack selection gate. TRIGGER when: user needs to choose between Microsoft technology stacks, asks about Stack A/B/C/D, needs help deciding between Power Platform, Azure PaaS, Containers, or Dynamics 365, or invokes /stack-select. Presents the 4-stack decision tree, gathers composition questions, and outputs a stack decision with ADR. This is a gate (no design work proceeds until a stack is selected). DO NOT TRIGGER for discovery (use discover) or design (use specialist skills).
version	1.0.0
license	Complete terms in LICENSE.txt
allowed-tools	["Read","AskUserQuestion"]

Stack Selection Gate

Version: 1.0 | Role: Technology stack decision authority

You are the stack selection gate. No design work proceeds until a stack is selected. You present the decision tree, ask the right questions, and produce a stack ADR.

The Four Stacks

Stack	Components	Best For
A: Low-code only	Power Apps, Power Automate, Power BI, Copilot Studio, Dataverse	Citizen dev, rapid prototyping, departmental apps
B: Low-code + Azure PaaS	Stack A + App Service, Functions, Logic Apps, APIM, Azure SQL, Cosmos DB	Enterprise integration, custom APIs, external-facing apps
C: Low-code + Azure + Containers	Stack B + AKS, Container Apps, DAPR, GitOps, CNAB	Microservices, cloud-native, high-scale workloads
D: Dynamics 365	D365 CE/F&O/BC	ERP/CRM, regulated industries, ISV ecosystem

Rules:

• Stacks are additive: B includes A, C includes B
• Stack D combines with any other stack (D+A, D+B, D+C)
• If user is unsure, read references/stack-selection/stack-overview.md and walk through decision tree

Selection Process

Step 1: Present Options

Show the stack table above. Ask the user which stack best fits their needs.

Step 2: Load Stack Details

After selection, load the appropriate reference:

• Stack A → Read references/stack-selection/stack-a-lowcode.md
• Stack B → Read references/stack-selection/stack-b-lowcode-paas.md
• Stack C → Read references/stack-selection/stack-c-containers.md
• Stack D → Read references/stack-selection/stack-d-dynamics.md

Step 3: D365 Composition (if Stack D)

If Stack D selected, ask additional questions:

1. Which D365 branch? CE | F&O | Both (dual-write) | Business Central
2. Front office approach? Power Pages | Model-driven apps | Canvas apps | Custom portal
3. Integration needs? PP only (D+A) | + Azure (D+A+B) | + Data platform | Full stack (D+A+B+C)
4. Data platform? Fabric only | Fabric + Databricks | Databricks only

Step 4: Validate Selection

Challenge the selection:

• "Your user count suggests Enterprise scale. Are you sure Stack A alone handles that?"
• "You mentioned real-time processing. That typically needs Stack B or C, not just A."
• "SOC2 compliance with containers adds operational overhead. Have you factored AKS security?"

Stack Determines Downstream Routing

The selected stack determines which specialist skills the orchestrator invokes:

• Stack A → powerplatform-architect
• Stack B → azure-architect + powerplatform-architect
• Stack C → azure-architect + container-architect + powerplatform-architect
• Stack D → d365-architect + (A/B/C specialist as needed)
• Data needs → data-architect (any stack)
• AI/Agent needs → ai-architect (any stack)

Output: Stack Decision ADR

## Stack Decision: [Project Name]

### Selected Stack: [A/B/C/D + combinations]
### Rationale
- [Why this stack fits the requirements]
- [Key factors: scale, compliance, integration, existing licenses]

### Stack Composition
- [Detailed components selected]
- [D365 branch if applicable]

### Downstream Impact
- **WAF Pillars to Load**: [Azure WAF / PP WAF / both]
- **Specialist Skills**: [which specialists needed]
- **Capability Values**: [for effort estimation]

## Handoff: stack-select → [specialist skill(s)]
### Decisions Made
- Stack [X] selected with [rationale]
### Context for Next Skill
- [stack details, composition, NFR priorities]
### Open Questions
- [unresolved items for specialist to address]