github/awesome-copilot / skills/azure-smart-city-iot-solution-builder
azure-smart-city-iot-solution-builder
VerifiedDesign and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| references/smart-city-solution-template.md | markdown | 1.3 KB |
references/smart-city-solution-template.md
View on GitHub# Smart City IoT Solution Template
Use this template to standardize outputs for each new smart city scenario.
## 1. Use case summary
- Domain:
- Stakeholders:
- Problem statement:
- Success metrics:
## 2. Device and data profile
- Device types and count:
- Telemetry schema:
- Ingestion rate:
- Command/control requirements:
- Retention policy:
## 3. Reference architecture
- Edge and field layer:
- Ingestion layer:
- Processing layer:
- Storage layer:
- API and integration layer:
- Monitoring and security layer:
## 4. NFR checklist
- Availability target:
- Latency target:
- Security controls:
- Data privacy constraints:
- DR strategy:
- Cost target:
## 5. Phased roadmap
### Phase 1 - Pilot
- Scope:
- Deliverables:
- Exit criteria:
### Phase 2 - Scale
- Scope:
- Deliverables:
- Exit criteria:
### Phase 3 - Optimize
- Scope:
- Deliverables:
- Exit criteria:
## 6. Initial backlog baseline
- Epic: Device onboarding and identity
- Epic: Telemetry ingestion and routing
- Epic: Real-time alerting and incident workflow
- Epic: Historical analytics and reporting
- Epic: Security and compliance hardening
- Epic: Governance and cost optimization
## 7. Risks
- Vendor/device interoperability gaps
- Network reliability in field locations
- Data quality issues and schema drift
- Over-retention that increases costs
- Ambiguity in operational ownership
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |