What problem does it solve? Running a platform-engineering and agentic delivery maturity assessment stalls when no single person can access every system. This Skill splits the work into permission-scoped increments run by the roles that already hold access, keeps raw evidence inside its approved boundary, and merges minimized findings into one auditable assessment state. ## Core Features & Use Cases - Increment-based engagement model: Nine cataloged increments (I1–I9) map repositories, CI/CD, Kubernetes, FinOps, security, data platforms, surveys, reconciliation, and Azure estate review to the roles authorized to run them, with least-privilege read-only access contracts. - Canonical state and delta merging: A single assessment-state.yaml with stable increment-prefixed evidence IDs, parallel delta files, immutable evidence records, and a reconciliation contract that marks claims confirmed, contradicted, or gap-filled. - Three separate maturity readings: Produces CNCF platform-engineering stages, ASDLC levels, and seven Agentic Developer Portal readiness gates as distinct outputs, never averaged into one score. - Use Case: A security engineer, a FinOps analyst, and a platform engineer each run their own read-only increment; the assessment lead merges the deltas, reconciles contradictions, and hands three separate ledgers to the reporting skill. ## Quick Start Ask the agent to plan a phased platform maturity assessment split by role and access, starting with whichever increments are already authorized.
