Repo Capability Map
Discover what each repository can do, classify capabilities by domain, assess maturity, and identify strategic gaps.
Purpose
While repository-health-analyzer asks "is the repo well-maintained?", this skill asks "what can this repo do, and what's missing?"
It produces a structured capability inventory across the entire workspace, enabling:
- Strategic planning against mission objectives
- Identification of capability gaps before they become blockers
- Cross-repo dependency awareness
- Maturity tracking over time
Capability Taxonomy
Two-level hierarchy: Domain > Capability Area
| Domain ID |
Domain Name |
Description |
ENG |
Engineering Analysis |
Simulation, modeling, structural/fatigue analysis |
DATA |
Data & Analytics |
Data pipelines, visualization, statistical analysis |
WEB |
Web & Frontend |
Websites, UI components, client-side applications |
BIZ |
Business Operations |
Admin tools, invoicing, client management |
INFRA |
Infrastructure & DevOps |
CI/CD, packaging, deployment, shared utilities |
KNOW |
Knowledge & Documentation |
Media, resumes, knowledge bases, training materials |
FIN |
Financial & Investments |
Portfolio tracking, financial modeling, reporting |
The taxonomy is discovered dynamically -- the agent maps findings to known domains but can create new ones if a repo doesn't fit.
Maturity Model
| Level |
Label |
Criteria |
| 1 |
Nascent |
Mentioned in mission/roadmap but no implementation exists |
| 2 |
Emerging |
Partial implementation, <50% test coverage, active WIP |
| 3 |
Established |
Working implementation with tests, docs, CLI/API available |
| 4 |
Mature |
Production-grade, 80%+ coverage, skills defined, decision history |
Assessment is based on observable artifacts (files exist, tests present, skills defined) -- not subjective judgments.
Analysis Methodology
For each repo, read files in priority order:
Tier 1 -- Declared Identity (highest confidence)
README.md -- mission, capabilities snapshot, featuresCLAUDE.md -- tech stack, project rules, domain keywords.agent-os/product/mission.md -- strategic phases, success metrics.agent-os/product/roadmap.md -- planned features, completion status
Tier 2 -- Structural Evidence
src/ directory tree -- module names, sub-packages.claude/skills/ -- domain skills (each skill = capability signal)pyproject.toml / package.json -- dependencies, entry pointstests/ and docs/ structure
Tier 3 -- Behavioral Evidence
git log --oneline -30 -- recent activity, development focusscripts/ directory -- automation capabilitiesdata/ / config/ contents -- data domains
Actions
| Action |
File |
Description |
| scan |
actions/scan.md |
Extract capabilities from one or all repos |
| gaps |
actions/gaps.md |
Analyze gaps against mission objectives |
| report |
actions/report.md |
Generate console summary + markdown report |
| compare |
actions/compare.md |
Side-by-side comparison between two repos |
Templates
| Template |
File |
Description |
| Repo Profile |
templates/repo-profile.md |
Per-repo capability profile |
| Capability Report |
templates/capability-report.md |
Full workspace capability report |
Integration Points
- repository-health-analyzer -- health gates capability scanning (unhealthy repos get flagged)
- work-queue -- gap analysis can feed
/work add items for uncovered objectives
- claude-reflect -- periodic reflection includes capability changes over time
- compliance-check -- repos missing CLAUDE.md receive lower maturity scores
Command Reference
See @.claude/commands/workspace-hub/repo-capability-map.md for usage.
1---2name: repo-capability-map3description: Analyzes repository modules for current capabilities, groups them by domain, and identifies strategic gaps against mission objectives4---5
6# Repo Capability Map
7
8> Discover what each repository can do, classify capabilities by domain, assess maturity, and identify strategic gaps.
9
10## Purpose
11
12While `repository-health-analyzer` asks "is the repo well-maintained?", this skill asks **"what can this repo do, and what's missing?"**
13
14It produces a structured capability inventory across the entire workspace, enabling:
15- Strategic planning against mission objectives
16- Identification of capability gaps before they become blockers
17- Cross-repo dependency awareness
18- Maturity tracking over time
19
20## Capability Taxonomy
21
22Two-level hierarchy: **Domain** > **Capability Area**
23
24| Domain ID | Domain Name | Description |
25|-----------|-------------|-------------|
26| `ENG` | Engineering Analysis | Simulation, modeling, structural/fatigue analysis |
27| `DATA` | Data & Analytics | Data pipelines, visualization, statistical analysis |
28| `WEB` | Web & Frontend | Websites, UI components, client-side applications |
29| `BIZ` | Business Operations | Admin tools, invoicing, client management |
30| `INFRA` | Infrastructure & DevOps | CI/CD, packaging, deployment, shared utilities |
31| `KNOW` | Knowledge & Documentation | Media, resumes, knowledge bases, training materials |
32| `FIN` | Financial & Investments | Portfolio tracking, financial modeling, reporting |
33
34The taxonomy is **discovered dynamically** -- the agent maps findings to known domains but can create new ones if a repo doesn't fit.
35
36## Maturity Model
37
38| Level | Label | Criteria |
39|-------|-------|----------|
40| 1 | **Nascent** | Mentioned in mission/roadmap but no implementation exists |
41| 2 | **Emerging** | Partial implementation, <50% test coverage, active WIP |
42| 3 | **Established** | Working implementation with tests, docs, CLI/API available |
43| 4 | **Mature** | Production-grade, 80%+ coverage, skills defined, decision history |
44
45Assessment is based on **observable artifacts** (files exist, tests present, skills defined) -- not subjective judgments.
46
47## Analysis Methodology
48
49For each repo, read files in priority order:
50
51### Tier 1 -- Declared Identity (highest confidence)
52- `README.md` -- mission, capabilities snapshot, features
53- `CLAUDE.md` -- tech stack, project rules, domain keywords
54- `.agent-os/product/mission.md` -- strategic phases, success metrics
55- `.agent-os/product/roadmap.md` -- planned features, completion status
56
57### Tier 2 -- Structural Evidence
58- `src/` directory tree -- module names, sub-packages
59- `.claude/skills/` -- domain skills (each skill = capability signal)
60- `pyproject.toml` / `package.json` -- dependencies, entry points
61- `tests/` and `docs/` structure
62
63### Tier 3 -- Behavioral Evidence
64- `git log --oneline -30` -- recent activity, development focus
65- `scripts/` directory -- automation capabilities
66- `data/` / `config/` contents -- data domains
67
68## Actions
69
70| Action | File | Description |
71|--------|------|-------------|
72| scan | `actions/scan.md` | Extract capabilities from one or all repos |
73| gaps | `actions/gaps.md` | Analyze gaps against mission objectives |
74| report | `actions/report.md` | Generate console summary + markdown report |
75| compare | `actions/compare.md` | Side-by-side comparison between two repos |
76
77## Templates
78
79| Template | File | Description |
80|----------|------|-------------|
81| Repo Profile | `templates/repo-profile.md` | Per-repo capability profile |
82| Capability Report | `templates/capability-report.md` | Full workspace capability report |
83
84## Integration Points
85
86- **repository-health-analyzer** -- health gates capability scanning (unhealthy repos get flagged)
87- **work-queue** -- gap analysis can feed `/work add` items for uncovered objectives
88- **claude-reflect** -- periodic reflection includes capability changes over time
89- **compliance-check** -- repos missing CLAUDE.md receive lower maturity scores
90
91## Command Reference
92
93See `@.claude/commands/workspace-hub/repo-capability-map.md` for usage.
majiayu000