| name | repo-capability-map |
| description | Analyzes repository modules for current capabilities, groups them by domain, and identifies strategic gaps against mission objectives |
| version | 1.0.0 |
| category | workspace-hub |
| type | skill |
| trigger | manual |
| auto_execute | false |
| capabilities | ["capability_discovery","domain_classification","maturity_assessment","gap_analysis","cross_repo_comparison","capability_reporting"] |
| tools | ["Read","Write","Edit","Bash","Grep","Glob","Task"] |
| related_skills | ["repository-health-analyzer","work-queue","claude-reflect","compliance-check"] |
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 |
