cloud-architect

Coordinates cloud architecture tasks, producing deliverables such as reference diagrams and actionable blueprints from natural language requests, while maintaining privacy by never logging raw inputs or outputs.

7|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill --skill cloud-architect-daemon-blockint-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-architect
Source: https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill/tree/main/cloud-architect
Command: npx skills add https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill --skill cloud-architect-daemon-blockint-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams define cloud strategy and architecture decisions to reduce ambiguity and rework during cloud initiatives.

Core Features & Use Cases

  • Well-Architected reviews and guardrail design for multi-account environments.
  • Reference architectures, landing zones, workload placement, and network/security segmentation guidance.
  • Architecture deliverables (ADR set, target architecture diagrams) to communicate decisions to stakeholders.

Quick Start

Draft a high-level cloud-architecture review plan using Well-Architected principles and produce ADRs and a reference diagram.

Frequently Asked Questions about cloud-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a cloud landing zone and when do I need one for multi-account environments?

A Well-Architected review evaluates cloud architecture against core pillars to identify risks and define guardrails. It helps teams satisfy security, cost modeling, and operational requirements during strategy definition and landing zone design.

How do I write an Architecture Decision Record for cloud strategy definition?

To design cloud architecture for multi-account environments, apply guardrails across strategy definition, landing zone design, and workload placement. This approach ensures proper security segmentation and yields ADRs with target architecture diagrams.

Can I use this for network and security segmentation in a multi-account setup?

Architecture deliverables include a set of ADRs and target architecture diagrams. These outputs explicitly communicate cloud strategy and landing zone design decisions to stakeholders, reducing ambiguity and rework during initiatives.

What's the best way to model costs and satisfy Well-Architected reviews?

This approach is suited for multi-account cloud environments requiring strict guardrails and Well-Architected reviews. It fits teams needing reference architectures, ADRs, and cost modeling to communicate complex cloud strategy decisions to stakeholders.