---
name: verify-a1
description: Verify adoption criterion A1 (Agent Context Availability) in the current project. Reports fulfillment level 0–3.
allowed-tools: Bash Read
---

# Verify A1 — Agent Context Availability

## Criterion Definition

| Level | Description |
|-------|-------------|
| 0 | No agent context files; agents must infer everything from raw code |
| 1 | Basic README or project description exists; agents have a starting point but no conventions or navigation guidance |
| 2 | CLAUDE.md or AGENTS.md provides project-specific guidance: conventions, architecture overview, key commands |
| 3 | Comprehensive agent context including architecture docs structured for agent consumption AND MCP servers exposing project knowledge (requirements, diagrams, runbooks) |

## Evidence

### Agent context files
!`ls CLAUDE.md AGENTS.md .claude/CLAUDE.md 2>/dev/null || echo "(none found)"`

### CLAUDE.md / AGENTS.md content quality
!`wc -l CLAUDE.md 2>/dev/null || wc -l AGENTS.md 2>/dev/null || echo "(no agent context file)"`
!`head -80 CLAUDE.md 2>/dev/null || head -80 AGENTS.md 2>/dev/null || echo "(no content)"`

### Sections in the agent context file (conventions, architecture, commands)
!`grep -i "convention\|command\|architecture\|run\|test\|build\|structure\|navigate\|workflow" CLAUDE.md AGENTS.md 2>/dev/null | head -20 || echo "(no key sections found)"`

### README presence and depth
!`ls README.md 2>/dev/null && wc -l README.md || echo "(no README.md)"`
!`head -30 README.md 2>/dev/null || echo "(no README)"`

### MCP server configuration (programmatic project knowledge)
!`cat .mcp.json 2>/dev/null || echo "(no .mcp.json)"`
!`cat .claude/settings.json 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); mcp=d.get('mcpServers',{}); print('MCP servers:', list(mcp.keys()) if mcp else 'none')" 2>/dev/null || echo "(no .claude/settings.json or no MCP servers)"`

### Architecture docs structured for agent consumption
!`find . -maxdepth 4 \( -iname "ARCHITECTURE.md" -o -iname "architecture.md" -o -iname "DESIGN.md" \) 2>/dev/null | grep -v node_modules | head -10 || echo "(no architecture docs)"`
!`find docs/ -name "*.md" 2>/dev/null | head -15 || echo "(no docs/ directory)"`

## Instructions

Analyse the evidence above and determine the fulfillment level for A1.

Scoring guide:
- **Level 0**: No CLAUDE.md, AGENTS.md, or equivalent exists. No README, or a README so minimal it provides no meaningful starting point.
- **Level 1**: A README or basic project description exists that tells an agent what the project is and how to navigate it at a high level. No project-specific conventions, key commands, or architecture guidance is present.
- **Level 2**: A CLAUDE.md or AGENTS.md (or equivalent) exists with substantive project-specific content: coding conventions, key commands (how to build, test, run), an architecture overview, or navigation hints. The file must go meaningfully beyond a README.
- **Level 3**: Level 2 is met AND architecture documentation is structured for agent consumption (e.g., machine-readable or well-organised in-repo docs) AND at least one MCP server exposes project knowledge (requirements, diagrams, runbooks) programmatically.

Report in exactly this format:

**A1 — Agent Context Availability**
- **Level**: [0 / 1 / 2 / 3]
- **Rationale**: [one or two sentences citing the specific evidence]