metrics.update-components

Type: commands | Track: Enterprise

Auto-scan the .claude/ directory and MANIFEST.json to update component counts in docs/static/data/components.csv. Delegates to meta-engineering-expert.

---

Quick Start

Invoke via ADLC command interface: /metrics:update-components

---

Component Types Scanned

Type	Scan Path	Description
Agents	.claude/agents/*.md	Constitutional AI agents
Commands	.claude/commands/**/*.md	Slash command definitions
Skills	.claude/skills/**/*.md	Reusable capability packages
MCPs	MANIFEST.json	MCP server configurations
Hooks	.claude/hooks/scripts/*.sh	Enforcement hooks
Rules	.claude/rules/*.md	Behavioral governance rules

---

Benefits

1. Single command to keep the marketplace component counts accurate — no manual counting
2. Feeds the Docusaurus marketplace dashboard with current inventory
3. Prevents DISTRIBUTED_VERSION_DUPLICATION — counts come from actual file scans, not hardcoded values
4. Evidence: writes updated components.csv with row-level counts and scan timestamp

---

When to Use

Attribute	Detail
Persona	Meta-Engineering Expert (MEE)
Trigger	Framework inventory drift — after adding new agents, commands, or skills during a sprint, or before a framework release when the marketplace component counts need to reflect the actual state
Business Value	Accurate component counts in the Docusaurus marketplace — prevents stale counts that mislead customers about the framework scope; one scan replaces manual counting across 310+ files
Frequency	Weekly

Example: As a Meta-Engineering Expert, I need to update component counts after adding 3 new commands in the sprint because the marketplace landing page shows the old count and the HITL wants accurate numbers in the sprint review. I run /metrics:update-components which scans all .claude/ subdirectories, counts each component type, and writes the updated counts to docs/static/data/components.csv with a scan timestamp.

Framework maintenance command. No coordination required for count updates.