1# Requirements Gathering
2 
3Collect project requirements through conversation before making architecture decisions.
4 
5## Categories
6 
7### 1. Classification
8 
9| Type | Description | Implications |
10|------|-------------|--------------|
11| POC | Proof of concept | Minimal infra, cost-optimized |
12| Development | Internal tooling | Balanced, team-focused |
13| Production | Customer-facing | Full reliability, monitoring |
14 
15### 2. Scale
16 
17| Scale | Users | Considerations |
18|-------|-------|----------------|
19| Small | <1K | Single region, basic SKUs |
20| Medium | 1K-100K | Auto-scaling, multi-zone |
21| Large | 100K+ | Multi-region, premium SKUs |
22 
23### 3. Budget
24 
25| Profile | Focus |
26|---------|-------|
27| Cost-Optimized | Minimize spend, lower SKUs |
28| Balanced | Value for money, standard SKUs |
29| Performance | Maximum capability, premium SKUs |
30 
31### 4. Compliance
32 
33| Requirement | Impact |
34|-------------|--------|
35| Data residency | Region constraints |
36| Industry regulations | Security controls |
37| Internal policies | Approval workflows |
38 
39### 5. Subscription Policies
40 
41After the user confirms a subscription, query Azure Policy assignments to discover enforcement constraints before making architecture decisions.
42 
43```
44mcp_azure_mcp_policy(command: "policy_assignment_list", subscription: "<subscriptionId>")
45```
46 
47| Policy Constraint | Impact |
48|-------------------|--------|
49| Blocked resource types or SKUs | Exclude from architecture |
50| Required tags | Add to all Bicep/Terraform resources |
51| Allowed regions | Restrict location choices |
52| Network restrictions (e.g., no public endpoints) | Adjust networking and access patterns |
53| Storage policies (e.g., deny shared key access) | Use policy-compliant auth |
54| Naming conventions | Apply to resource naming |
55 
56> ⚠️ **Warning:** Skipping this step can cause deployment failures when Azure Policy denies resource creation. Checking policies here prevents wasted work in architecture and generation phases.
57 
58Record discovered policy constraints in `.azure/deployment-plan.md` under a **Policy Constraints** section so they feed into architecture decisions.
59 
60## Gather via Conversation
61 
62Use `ask_user` tool to confirm each of these with the user:
63 
641. Project classification (POC/Dev/Prod)
652. Expected scale
663. Budget constraints
674. Compliance requirements (including data residency preferences)
685. Subscription and policy constraints (confirm subscription, then check policies automatically)
696. Architecture preferences (if any)
70 
71## Document in Plan
72 
73Record all requirements in `.azure/deployment-plan.md` immediately after gathering.
74