asdlc-maturity-assessment

Scores organizational agentic software-delivery maturity across eight paths and five ASDLC levels.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill asdlc-maturity-assessment-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asdlc-maturity-assessment
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/platform-assessment/skills/asdlc-maturity-assessment
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill asdlc-maturity-assessment-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Organizations adopting AI coding agents struggle to answer "how mature are we?" with evidence rather than opinion. This Skill turns that question into a defensible, leveled diagnosis by scoring all eight delivery paths against the five-level Agentic Software Development Lifecycle (ASDLC) model and producing a concrete roadmap to the next level. ## Core Features & Use Cases - 8-path × 5-level scoring rubric: Scores every delivery path (retrieve context, implement, validate, promote, deploy, observe, remediate, dispatch) from Level 0 (human is the loop) through Level 3 (human as orchestrator), with Level 4 treated only as a speculative outlook. - Evidence-backed audit playbook: Pulls proof from systems of record — work trackers (Jira, Azure Boards, GitHub Issues), repo settings and branch protections, CI/CD pipelines (YAML vs. Classic), and agent attribution signals like bot identities and commit trailers. - Quantitative measurement layer: Segments DORA metrics by agent involvement, tracks agent-PR merge rates and adoption telemetry, and applies the DORA AI Capabilities foundations check. - Regulated-industry overlay: Layers workspace-level governance, privilege separation, and policy-as-code requirements for finance, government, and healthcare contexts. - Use Case: A platform engineering lead asks for an agentic readiness review before a coding-agent rollout; the Skill audits repos, pipelines, and trackers, scores the org at Level 1 with partial Level 2 evidence, and delivers a gap report with a next-level roadmap. ## Quick Start Use the asdlc-maturity-assessment skill to score our organization's agentic delivery maturity and build a roadmap to the next level.

Frequently Asked Questions about asdlc-maturity-assessment

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

FAQPage Schema
How do I assess my organization's AI coding agent maturity?

Score each of the eight delivery paths (retrieve context, implement, validate, promote, deploy, observe, remediate, dispatch) against the five ASDLC levels using production evidence. The organization's level is the highest level whose full path pattern is evidenced, with partial states reported explicitly.

What are the levels of the Agentic Software Development Lifecycle?

The ASDLC defines Level 0 (human is the loop), Level 1 (human in the loop with IDE assistance), Level 2 (human on the loop with dispatched agents and validation retry loops), Level 3 (human as orchestrator with risk-classified auto-promotion), and Level 4 (fully autonomous, treated only as a speculative outlook).

What evidence is needed to score agentic maturity Level 2?

Level 2 requires a dispatch-work-to-agents capability, agent identity tracked separately from humans, validation running as an automated retry loop before human review, and policy-as-code gates such as OPA, Kyverno, or Checkov in the pipeline. Evidence comes from trackers, repo settings, and CI/CD audit.

How do I measure which code was written by AI agents?

Audit bot identities, commit signatures, Co-authored-by trailers, and PR authorship across both commit history and pull requests. Squash merges can erase commit-level attribution, so checking only one channel undercounts agent-authored work.

Does this assessment work for regulated industries like finance or healthcare?

Yes, a regulated-industry overlay adds workspace-level governance, privilege separation, PR-only agent workflows, and policy-as-code requirements. These controls do not change level definitions but gate how quickly an organization can safely advance.

When should an organization not be scored at Level 4?

Level 4 is never assigned as a score because essentially no broad production examples exist. Instead, record forward indicators such as self-healing remediation decision trees or self-improving validation, while scoring the organization at most Level 3.