data-center-design-execution-lead

Name: data-center-design-execution-lead
Author: rade-nugroho

github.com/rade-nugrohoCloud & DevOps1241 installsUpdated 23w ago

About data-center-design-execution-lead

A skill for teams planning and delivering data center facilities, from new data halls and colo deployments to cloud extensions. It covers requirements, power and cooling, physical layout, connectivity, commissioning, and handoff.

Key features

01Define facility requirements and site strategy
02Plan power chains and cooling capacity
03Design rack, aisle, and cable layouts
04Plan carrier and cloud connectivity
05Coordinate procurement, installation, and commissioning
06Prepare acceptance tests and operations handoff

Use cases

01Compare build, colo, and cloud extension options
02Estimate current and future rack and power needs
03Review electrical diagrams and rack layouts
04Create commissioning checklists and operations runbooks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rade-nugroho/agentic-enteprises-skill --skill data-center-design-execution-lead

After installing, type/data-center-design-execution-leadin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/

execution_commissioning.md

facility_requirements.md

network_connectivity.md

operations_handoff.md

physical_layout.md

power_cooling.md

Details

From the project README

Data Center Design Execution Lead

When to Use

Define requirements for a new data hall, cage, or colo deployment
Compare build vs colo vs cloud extension for a workload footprint
Size power, cooling, and rack count for current and 3–5 year growth
Review mechanical/electrical single-line diagrams and rack elevations
Plan hot/cold aisle, containment, and cable pathways
Specify network demarc, cross-connects, and latency to cloud regions
Run design → procurement → install → commissioning → handoff
Prepare acceptance tests and operations runbooks for facilities team

When NOT to Use

Terraform, cloud networking, managed Kubernetes → infrastructure-engineer
Helm, cluster add-ons, pod troubleshooting → cluster-deployment-engineer
Application integration ADRs → senior-system-architecture
Multi-team software program RAID → technical-program-manager
SOC 2 control catalog without facility scope → compliance-engineer
Physical security policy program only → cybersecurity, information-security-engineer
Executive comms for launches → communication-lead
Utilization, GPU supply forecast, consolidation, refresh → data-center-compute-supply-efficiency
Multi-site roadmap, portfolio funding, steering → data-center-portfolio-planning-execution-lead
Delivery schedule, rack-ready gates, construction RAID → senior-data-center-capacity-delivery-manager

Related skills

Need	Skill
Hybrid on-prem virtualization patterns	`infrastructure-engineer`
Workloads hosted in on-prem K8s	`cluster-deployment-engineer`
Large build program coordination	`technical-program-manager`
Physical/logical security controls	`cybersecurity`, `information-security-engineer`
Compliance evidence for facilities	`compliance-engineer`
Stakeholder and exec updates	`communication-lead`
Rollout of apps into new site	`deployment-strategist`
Compute supply and resource efficiency	`data-center-compute-supply-efficiency`
Enterprise DC portfolio planning	`data-center-portfolio-planning-execution-lead`
Capacity delivery program	`senior-data-center-capacity-delivery-manager`
On-site install, labeling, acceptance	`field-services-engineer`

Core Workflows

1. Requirements and site strategy

Capture:

Workload type (enterprise IT, HPC/GPU, edge)
Availability target (tier intent, RTO/RPO for facility)
Growth: racks, kW, network ports by year
Constraints: geography, latency to users/cloud, sustainability, budget

Decide: own build, colo cage, or cloud-only with small edge.

See references/facility_requirements.md.

2. Power and cooling

Design power chain: utility → ATS/STS → UPS → PDU → rack
Size for peak kW/rack (air vs liquid, GPU trays)
Cooling: CRAC/CRAH, containment, setpoints per ASHRAE class
Target PUE and measurement points

See references/power_cooling.md.

3. Physical layout

Rack rows, aisle width, floor load (lbs/sq ft)
Hot/cold containment; overhead vs underfloor delivery
Cable trays, fiber pathways, ladder rack
Staging, spares, and restricted zones

See references/physical_layout.md.

4. Network and connectivity

Meet-me room, carrier diversity, cross-connect model
Core/distribution/toR switching for facility (distinct from app network design in cloud)
Latency and bandwidth to primary cloud region for hybrid

See references/network_connectivity.md.

5. Execution and commissioning

Phase	Deliverables
Design	BoM, drawings, capacity model sign-off
Procure	Long-lead gear tracked (switching, PDUs, genset)
Install	MEP fit-out, rack/stack, labeling standard
Commission	IST/FAT, red-tag clearance, integrated tests
Handoff	DCIM, monitoring, as-built, ops training

See references/execution_commissioning.md.

6. Operations handoff

DCIM asset records match labels and diagrams
Environmental and power alarms to NOC
Maintenance windows and vendor SLAs documented
Runbooks: escort, smart hands, emergency power-down

See references/operations_handoff.md.

Output standards

Capacity table: rack ID, kW design, weight, network Uplinks
One-line diagram summary (power and cooling) with margins noted
Commissioning checklist with pass/fail and owner
Risks: single points of failure, lead-time items, permit dependencies

When to load references

Site, tier, capacity → references/facility_requirements.md
Power, UPS, cooling, PUE → references/power_cooling.md
Racks, aisles, containment → references/physical_layout.md
Carriers, MMR, hybrid links → references/network_connectivity.md
Build phases and commissioning → references/execution_commissioning.md
DCIM and ops → references/operations_handoff.md

Comments

Markdown supported

Details

Author: rade-nugroho
Repository: rade-nugroho/agentic-enteprises-skill
Category: Cloud & DevOps
Installs: 41
GitHub stars: 12

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.