Maturity Matrix
Matrix/Development

Development

How developers work with AI day-to-day. From sidebar chat to fleet agents.

4capabilities20levels60practices60guides
The matrix · at a glance
Capability ↓
Maturity →
L1 · Stage 01
Ad-hoc
L2 · Stage 02
Guided
L3 · Stage 03
Systematic
L4 · Stage 04
Optimized
Sweet spot
L5 · Stage 05
Autonomous
01
Coding Agent Usage
02
Context Engineering
03
Code Review & Quality
04
Testing Strategy
Capability 01 · Development

Coding Agent Usage

How your team uses AI coding assistants - from autocomplete to autonomous agent fleets.

L1 · Stage 01Ad-hoc
Criteria - what to measure
  1. 01At least one AI coding assistant (Copilot, Cursor, Claude Code) is installed and active for at least one developer
  2. 02AI autocomplete or chat is used at least once per week by the team
  3. 03Developers have access to AI chat in their IDE sidebar
  4. 04Team has experimented with AI-assisted code generation on non-critical tasks
L2 · Stage 02Guided
Criteria - what to measure
  1. 01At least one agentic IDE (Cursor, Windsurf, or Claude Code) is used by 50%+ of the team
  2. 02CLAUDE.md, .cursorrules, or equivalent agent instruction file exists in 100% of active repositories
  3. 03Agents operate in agentic/YOLO mode (multi-step edits without per-step approval)
  4. 04Developers use two or more AI tools in parallel (e.g., Copilot + Claude Code)
  5. 05Agent instruction files are reviewed and updated at least quarterly
L3 · Stage 03Systematic
Criteria - what to measure
  1. 01CLI agents (Claude Code, Codex) are the primary coding interface for 50%+ of feature work
  2. 02Per-team or per-repo rules files exist and are maintained with code review
  3. 03Coding conventions are written as explicit, agent-parseable rules (not implicit tribal knowledge)
  4. 04Agent usage is tracked per developer and per repository
  5. 05Agent instruction files follow a standardized template across the organization
L4 · Stage 04OptimizedMost teams aim here
L5 · Stage 05Autonomous
Capability 02 · Development

Context Engineering

What information agents receive about your codebase, architecture, and conventions.

Capability 03 · Development

Code Review & Quality

How AI-generated code is reviewed, validated, and approved before merging. AI code has 1.7x more issues and 2.74x more security vulnerabilities - review is now critical infrastructure.

L2 · Stage 02Guided
Criteria - what to measure
  1. 01AI-assisted review tool (CodeRabbit, Qodo, or equivalent) is active on all repositories
  2. 02Linter rules are configured and run in CI on every PR
  3. 03PRs clearly indicate whether code is AI-generated or AI-assisted (labels, tags, or commit metadata)
  4. 04AI review suggestions are triaged (accepted/rejected) rather than ignored
  5. 05Linter configuration is committed to the repository and versioned
L3 · Stage 03Systematic
Criteria - what to measure
  1. 01AI review agent runs as a first-pass reviewer on every PR before human review
  2. 02Lint rules enforce architectural standards (not just style) - the "Bug to Codify to Lint Rule" pipeline is active
  3. 03At least 3 architectural guardrail rules have been created from past bugs or incidents
  4. 04AI review agent findings are categorized by severity (info, warning, blocking)
  5. 05New lint rules are proposed automatically when recurring review comments are detected
Capability 04 · Development

Testing Strategy

How tests are written, maintained, and validated in an AI-assisted workflow. A test "oracle" is the source of truth for what a test's correct result should be.

L2 · Stage 02Guided
Criteria - what to measure
  1. 01Agents generate unit tests; humans write acceptance tests
  2. 02Flaky test quarantine process is active (flaky tests are isolated, not deleted)
  3. 03Humans define the expected results for important paths (not just snapshotting current output)
  4. 04Flaky test count is tracked and reported weekly
  5. 05Quarantined tests have a resolution SLA (e.g., fix or delete within 30 days)
L3 · Stage 03Systematic
L5 · Stage 05Autonomous
Criteria - what to measure
  1. 01Test suite is self-healing (agent detects broken tests, diagnoses root cause, fixes without human input)
  2. 02Production logs automatically generate regression tests for observed failures
  3. 03Agents detect edge cases, write tests, fix bugs, and ship - full autonomous loop
  4. 04Self-healing test updates are validated by mutation testing before merge
  5. 05Production-to-test pipeline latency is under 1 hour (failure observed to regression test committed)
Climb the matrix

You don't have to figure this out alone.

Every level in this matrix has a path. Read the playbooks the teams that have climbed it wrote. Run the assessment with our consultants. Start where you are.

Live with Visdom

Book an AI Maturity Assessment session with your team.

We walk you through all four perspectives, score where you actually are, and leave you with a 90-day plan to climb in the dimensions that matter most.

Book an assessment See what's included90-day plan - scored assessment - coaching
Author Commentary

The July 2026 zeitgeist is bring it home.

After May's invoice, June was the month teams went looking for a way to depend on AI without being owned by it - and the case for sovereignty made itself. On June 9 Anthropic launched Fable 5 and Mythos 5, its most capable models ever; on the evening of June 12 it disabled them worldwide under a US export-control order, and they were still dark over a week later. Whatever you built on top of Fable 5 stopped working overnight, through no fault of your own. The most capable model is worth less than the model you can still run tomorrow.

The alternative got real the same month. Open-weight coding models crossed the line from toy to tool: GLM-5.2 (Z.ai, MIT) beat GPT-5.5 on SWE-bench Pro at a sixth of the cost, and Kimi K2.7-Code shipped with day-one vLLM/SGLang support - both runnable on your own hardware. The job is still decomposition and oversight, but now part of the job is deciding where the agent runs and what it is allowed to remember. Two June shifts matter here: memory moved beyond RAG (Anthropic dropped vector search in Claude Code for agentic grep, and Microsoft's FastContext repo-explorer subagent cut coding-agent tokens up to 60%), and review moved past pass-rate (FrontierCode found over half of SWE-bench results are "unmergeable slop" and scored even Opus 4.8 at 13.4% on mergeability). Keep held-out oracles, score mergeability not green checkmarks, and reject code you cannot understand even when CI is green. The harness is the part you own - and in June the field finally named the discipline of building it. After a year of "AI-native engineering," the cascade became explicit: prompt → context → harness → loop engineering (Addy Osmani, LangChain, Loopcraft), with two dozen-plus loop and meta-harness tools shipping in the month. That is the second half of sovereignty: when the model is swappable, the loop you stack around it - play, test, fix, verify, improve - is where your leverage actually lives.

Other perspectives