ai-engineering-maturity

Assess organizational AI tooling adoption across eight engineering maturity stages.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/ndestates/ndestates-website --skill ai-engineering-maturity-ndestates
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ai-engineering-maturity
Source: https://github.com/ndestates/ndestates-website/tree/main/.copilot/skills/ai-engineering-maturity
Command: npx skills add https://github.com/ndestates/ndestates-website --skill ai-engineering-maturity-ndestates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams adopt AI coding tools unevenly, creating drift, islands, and ungoverned agent usage. This Skill provides a structured 8-stage framework to diagnose where a team or organization sits in AI engineering maturity and plan the next concrete advancement step without skipping foundational stages. ## Core Features & Use Cases - Stage Diagnosis: Maps current AI tooling practices (shared context files, skills, prompts, MCP servers, guardrails) to one of eight maturity stages from vacuum to autonomous factory. - Advancement Planning: Surfaces one concrete recommended next step per session, grounded in governance, shared context, and eval prerequisites. - Governance Alignment: Cross-references security checklists, git workflow guardrails, and cache-first prompts to ensure AI amplifies good practices rather than bad ones. - Use Case: During a standup or planning session, invoke the Skill to assess whether the team is at Stage 2 (individual drift) versus Stage 4 (standardization), and identify the specific gap—such as missing shared prompt libraries or absent PR gates on agent output. ## Quick Start Ask the AI to assess the team's current AI engineering maturity stage and recommend one concrete advancement step using this framework.

Frequently Asked Questions about ai-engineering-maturity

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

FAQPage Schema
How do I assess my team's AI engineering maturity level?▼

Map current practices against the 8 stages: check whether developers use ad-hoc prompts (Stage 1-2), teams have shared context files and skills (Stage 3-4), or agents run on shared infrastructure (Stage 7-8). The Skill provides assessment questions and project mapping guidance for each stage.

What are the 8 stages of AI engineering maturity?▼

The stages are: vacuum, drift, islands, standardization bet, workflow redesign, operating system, bright factory, and autonomous factory. They progress from ungoverned individual AI usage to agents running scheduled tasks on shared, observable infrastructure with evals gating every merge.

Why should teams not skip AI maturity stages?▼

Skipping stages means adopting autonomous agents without governance, testing, and shared context foundations, which is how projects get canceled. The friction of the current stage provides the evidence and motivation that justifies the next stage's investment.

How does shared context engineering prevent AI adoption drift?▼

Shared context engineering encodes knowledge once in repository artifacts like AGENTS.md files, curated skill and prompt libraries, and project memory. This moves standards out of individual heads into the system, preventing the Stage 2 drift where engineers develop divergent personal AI setups.

When should security governance be added to AI tooling?▼

Security and governance belong at Stage 4, before scaling AI usage. This includes SSO, secret scanning, PR gates on agent output, audit logs, and approved models behind a gateway, applied to any change involving skills, agents, prompts, or MCP servers.