platform-architect

Designs Internal Developer Platform strategy, reference architecture, governance, and maturity roadmaps.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/lurodrisilva/personal-skills --skill platform-architect-lurodrisilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-architect
Source: https://github.com/lurodrisilva/personal-skills/tree/main/platform-engineering/platform-architect
Command: npx skills add https://github.com/lurodrisilva/personal-skills --skill platform-architect-lurodrisilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Platform engineering leaders struggle to turn business intent into a coherent Internal Developer Platform (IDP) strategy: deciding which capabilities to build versus buy, designing golden paths, structuring platform teams, measuring developer outcomes, and recording architecture decisions. This Skill provides the distinguished-architect playbook for those decisions while delegating all implementation to concrete infrastructure skills. ## Core Features & Use Cases - Strategy & Reference Architecture: Applies platform-as-a-product thinking, build-vs-buy decision trees, Wardley mapping, technology radar governance, and the five IDP planes (Developer Control, Integration & Delivery, Monitoring & Logging, Security, Resource) with capability-to-implementer delegation. - Org Design, Metrics & Governance: Designs Team Topologies interaction modes, DORA + SPACE + adoption scorecards, MADR-style ADR/RFC processes, and CNCF maturity model assessments with sequenced roadmaps. - Read-Only Assessment Scripts: Ships three bash tools — dora-metrics-report.sh (DORA proxies from git history), adr-lint.sh (MADR structure linting), and platform-maturity-scan.sh (IDP maturity signal detection). - Use Case: A principal architect asked to "define our platform strategy" uses this Skill to produce an investment thesis, a golden-path spec, a Team Topologies interaction map, a DORA baseline scorecard, and a CNCF maturity assessment — then hands Terraform, Crossplane, and GitOps implementation to sibling skills. ## Quick Start Use the platform-architect skill to assess our platform maturity and draft a golden-path spec for shipping a stateless HTTP service.

Frequently Asked Questions about platform-architect

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

FAQPage Schema
How do I design an Internal Developer Platform strategy?▼

Start with platform-as-a-product framing: name the user, outcome, and metric for each capability before building. Map capabilities to the five IDP planes, decide build versus buy with a radar entry and investment thesis, then delegate implementation to concrete IaC and GitOps skills.

How to measure platform engineering success with DORA metrics?▼

Track the balanced DORA four keys — deploy frequency, lead time for changes, change-fail rate, and recovery time — plus SPACE and platform adoption/NPS. The included dora-metrics-report.sh script generates read-only proxies from git history to start the baseline conversation.

What is the CNCF Platform Engineering Maturity Model?▼

It assesses platforms across five aspects — Investment, Adoption, Interfaces, Operations, Measurement — at four levels from Provisional to Optimizing. The guidance is to fix the weakest load-bearing aspect first and never skip levels, such as building a portal before metrics exist.

Does this skill write Terraform or Kubernetes manifests?▼

No. It owns strategy, reference architecture, org design, metrics, and governance only, and deliberately delegates every implementation to sibling skills for Terraform, Crossplane, GitOps, observability, FinOps, and security. This keeps the decide-versus-build boundary sharp.

How do I write an ADR using the MADR format?▼

Create a NNNN-title.md file with a Status field, Context, Decision drivers, Considered options, Decision outcome, and Consequences sections. The adr-lint.sh script validates an ADR directory against this structure, flagging missing sections, duplicate numbers, and dangling Superseded-by references.

When should a platform team use collaboration versus X-as-a-Service?▼

X-as-a-Service is the default and destination mode for stable, well-understood capabilities. Collaboration is a time-boxed mode for co-designing new capabilities, and Facilitating fits when a team lacks a skill rather than a service; never-ending collaboration signals a missing abstraction.