platform-engineering

Plugin platform-engineering in BittahCriminal/platform-engineering-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (14)

• ai-native-platform

  Platform engineering for AI-assisted and agentic software development — the four levels of agentic development, workspace-level governance for AI coding agents (including regulated industries), and the AI-native platform blueprint (model hubs, GPU templates, golden paths for AI workloads). Use when

• architect-blueprint

  Capstone skill — reads every .platform/** artifact plus platform-blueprint's reference model and renders one organization-specific IDP/ADP blueprint document (Markdown or Notion), scored against an agentic-DevOps maturity rubric. Use when synthesizing discovery, persona, workload, product, permissio

• architect-infra-discovery

  Discovers real infrastructure across cloud and on-prem/local providers (Azure, AWS, GCP, Kubernetes) and normalizes it into the shared Resource schema. Use when starting a platform blueprint for a specific organization and no inventory exists yet, or when the inventory needs to be refreshed against

• architect-permissions-mapper

  Normalizes Azure RBAC/Entra ID, AWS IAM, and Kubernetes RBAC into one IdentityBinding model, then flags over-privileged, cross-boundary, orphaned, and unowned access. Use when mapping permissions boundaries or auditing IAM/RBAC posture for a discovered environment.

• architect-persona-generator

  Clusters discovered identity bindings and org group data into discrete platform personas mapped onto the five-plane model, including emerging agent personas (Cluster Doctor, coding agents). Use when defining who a platform serves, building a persona-aware onboarding flow, or scoping which stakeholde

• architect-product-catalog

  Packages discovered workloads and golden-path patterns into a self-service product catalog — each entry a golden path with an SLA and an owning persona. Use when defining what a platform's self-service menu should contain, deciding whether a capability should be exposed as a product versus a one-off

• architect-work-sync

  Adapter-based bridge from discovered platform entities (personas, workloads, permission gaps) to whatever work-tracking system the org already uses — Linear, Jira, GitHub, or Azure DevOps — detected at runtime. Never files a ticket silently; always drafts for human approval. Use when a discovered ga

• architect-workload-catalog

  Groups discovered resources into Score-style workload definitions with a closed type taxonomy (web-service, batch-job, ml-training, data-pipeline). Use when normalizing raw infrastructure into meaningful application-level units, defining what "a workload" means for a specific platform, or scoping au

• cloud-dev-environments

  Cloud Development Environments (CDEs) as a platform capability — preconfigured on-demand workspaces, the inner-loop counterpart to an IDP. Use when evaluating or rolling out CDEs (Coder, Gitpod, Codespaces, DevPod), fixing slow onboarding or works-on-my-machine problems, securing source code off lap

• cluster-lifecycle

  Kubernetes cluster lifecycle management as a platform product — Day 0 blueprints, Day 1 provisioning, Day 2 operations, and fleet management at scale. Use when designing cluster architecture, planning upgrades or patching, managing multiple clusters, defining cluster templates/blueprints, setting up

• platform-blueprint

  Reference architecture for scaffolding an Internal Developer Platform — the five-plane model, platform personas and what each consumes/creates, golden paths, design principles, and the sovereignty decision axis. Use when designing or reviewing an IDP, choosing platform tooling (portal, orchestrator,

• platform-observability

  Observability as a platform capability — OpenTelemetry standardization, cross-signal correlation, auto-instrumentation, dashboards-as-code, and SLO-based reliability. Use when designing or reviewing platform observability, instrumenting services, choosing telemetry tooling, setting up dashboards/ale

• platform-security

  Vulnerability management as a platform capability — shift down (not left), hardened base images, policy-as-code guardrails, SBOMs, and self-service remediation. Use when designing platform security, handling CVE scanning and prioritization, choosing security tooling (Trivy, Grype, Syft, OPA, Kyverno

• platform-state-of-play

  Current platform engineering benchmarks and trends (2025 State of Platform Engineering Vol 4, n=518; State of AI in Platform Engineering, n=242) for justifying platform decisions with data. Use when building a business case for platform investment, benchmarking a platform team (budget, metrics, matu