data-center-portfolio-planning-execution-lead

Name: data-center-portfolio-planning-execution-lead
Author: rade-nugroho

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

About data-center-portfolio-planning-execution-lead

A skill for teams planning and delivering multi-site data center portfolios. It covers capacity roadmaps, investment prioritization, execution governance, hybrid and exit strategies, and executive reporting.

Key features

01Create multi-site capacity roadmaps
02Roll up regional demand and supply gaps
03Rank investments and funding choices
04Govern stage gates, risks, and dependencies
05Plan cloud, colo, and exit strategies
06Prepare portfolio status reports

Use cases

01Plan multi-year data center capacity
02Choose projects within a fixed capex budget
03Coordinate concurrent site builds and expansions
04Prepare steering or board status updates

Install

Copy the command and run it in a terminal.

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

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

Bundled files

References and scripts installed along with SKILL.md.

references/

capacity_roadmap.md

execution_governance.md

hybrid_exit_strategy.md

investment_prioritization.md

portfolio_charter.md

steering_reporting.md

Details

From the project README

Data Center Portfolio Planning & Execution Lead

When to Use

Build or refresh a multi-site data center capacity roadmap (3–5+ years)
Prioritize competing DC investments under a fixed capex envelope
Run portfolio governance: stage gates, RAID, dependencies between DC projects
Align regional strategy (latency, sovereignty, DR, cloud burst)
Consolidate business cases from site leads into one portfolio narrative
Track execution across concurrent builds, expansions, refreshes, and exits
Prepare steering or board-level DC portfolio status
Decide build vs colo vs extend vs cloud at portfolio level

When NOT to Use

Single facility design, MEP, commissioning → data-center-design-execution-lead
Server/GPU utilization, consolidation, refresh tactics → data-center-compute-supply-efficiency
Multi-team software program (no DC portfolio) → technical-program-manager
Corporate strategy, operating model, issue trees → business-consultant
Terraform, VPC, K8s foundation → infrastructure-engineer
K8s cluster operations → cluster-deployment-engineer
Launch messaging only → communication-lead
MW/rack delivery program and readiness gates → senior-data-center-capacity-delivery-manager

Related skills

Need	Skill
Infrastructure capex policy and capitalization	`director-infrastructure-capex-accounting`
One site design and build execution	`data-center-design-execution-lead`
Compute supply and efficiency	`data-center-compute-supply-efficiency`
Cross-functional software delivery program	`technical-program-manager`
Investment narrative and options	`business-consultant`
Hybrid cloud technical patterns	`infrastructure-engineer`
Compliance evidence for facilities	`compliance-engineer`
Executive updates	`communication-lead`
Capacity delivery execution	`senior-data-center-capacity-delivery-manager`

Core Workflows

1. Portfolio charter and scope

Define:

Sites in scope — owned, colo, edge, planned
Horizon — planning years and refresh cycles
Constraints — capex ceiling, power at utility, sustainability targets
Decision rights — steering, stage gates, who owns site DRIs

See references/portfolio_charter.md.

2. Capacity and demand rollup

Aggregate demand by region (kW, racks, GPUs) from engineering and product
Map to supply per site (committed, available, planned)
Expose gaps by quarter and region
Flag single points of failure (one site, one carrier, one cooling plant)

See references/capacity_roadmap.md.

3. Investment prioritization

Score initiatives: strategic fit, risk reduction, NPV/TCO, dependency unlock, time criticality.

Output: ranked backlog, funded / deferred / kill, and tradeoff narrative.

See references/investment_prioritization.md.

4. Execution governance

Stage gates — concept → approved → execute → operate
Portfolio RAID — risks that span sites (power, lead time, vendor)
Dependency map — e.g. network build before hall acceptance
Integrate site-level status from data-center-design-execution-lead DRIs

See references/execution_governance.md.

5. Hybrid and exit strategy

Portfolio rules for cloud burst vs committed metal
Site exit or consolidation when utilization and TCO favor move
Contract and migration dependencies

See references/hybrid_exit_strategy.md.

6. Steering reporting

Monthly/quarterly: portfolio health (RAG), spend vs plan, milestone slip, top risks, decisions needed.

See references/steering_reporting.md.

Output standards

One-page portfolio summary + detailed initiative register
Roadmap by region (kW/racks/GPUs) with assumptions stated
Prioritization scorecard with explicit tradeoffs
Decision log for steering (what was decided, what was deferred)
No duplicate site engineering detail — link to site workstreams

When to load references

Charter and roles → references/portfolio_charter.md
Multi-site roadmap → references/capacity_roadmap.md
Scoring and funding → references/investment_prioritization.md
Gates, RAID, dependencies → references/execution_governance.md
Cloud, colo, exit → references/hybrid_exit_strategy.md
Steering pack → references/steering_reporting.md

Comments

Markdown supported

Details

Author: rade-nugroho
Repository: rade-nugroho/agentic-enteprises-skill
Category: Cloud & DevOps
Installs: 38
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.