| name | domain-gap-to-issue-roadmap |
| description | Deep multi-repo ecosystem audit → domain gap matrix → structured GitHub issue roadmap with epics. Use when the user wants to assess capabilities across repos and create a backlog of work items covering code, data, and documentation gaps. |
| version | 1.0.0 |
| category | github |
| type | skill |
| trigger | manual |
| related_skills | ["issue-portfolio-triage","dark-intelligence-workflow","research-literature"] |
| tags | ["ecosystem-audit","issue-creation","gap-analysis","roadmap","field-development","naval-architecture","geotechnical"] |
Domain Gap → Issue Roadmap
Audit engineering domains across a multi-repo ecosystem, map what exists vs what's missing
(code, data, standards, documentation), then create structured GitHub issues organized
into epics and phases.
When to Use
- User asks to "assess", "map", or "inventory" capabilities across repos
- User wants GitHub issues for future work based on gap analysis
- Multiple repos contribute to the same engineering domain (e.g., digitalmodel + worldenergydata)
- Dark intelligence / Excel extraction needs to be mapped against existing code
- User wants to understand code-vs-data-vs-documentation coverage
Methodology — 3 Phases
Phase 1: Parallel Deep Audit (delegate_task with 3 subagents)
Spawn 3 parallel subagents, each covering a different investigation axis:
Subagent 1 — Code & Extraction Inventory
- Search for all source files by domain (module counts, function counts, LOC)
- Find dark-intelligence extraction outputs (YAML archives, calculations.py stubs)
- Map extraction pipeline scripts and their current state
- Identify what's been extracted but NOT promoted to code
Subagent 2 — Conversion Infrastructure & Data Assets
- Search for Excel files, scraping outputs, CSV databases
- Find existing conversion scripts and their capabilities
- Map data registries, catalogs, and indexes
- Check external data sources (SubseaIQ, BSEE, SODIR, etc.)
Subagent 3 — Standards, Documentation & Module Registries
- Search standards-transfer-ledger for done/gap/reference status
- Find domain coverage reports and capability vision docs
- Map downloaded vs cataloged-only reference documents
- Identify test coverage by domain
Phase 2: Cross-Reference & Gap Matrix
After subagent results return, build the gap matrix:
Domain | Code Files | Standards Done/Gap | Excel Sources | Extractions | Tests | Docs
-------|-----------|-------------------|---------------|-------------|-------|-----
struct | 166 | 12/24 | yes | 2 POC | some | good
hydro | 154 | 0/0 | yes | none | some | good
geotech| 4 | 2/0 | 1 yaml | 1 POC | some | weak
...
Key cross-references to build:
- Excel dark intelligence → existing code modules (what's extracted but not wired?)
- Standards ledger gaps → code gaps (which standards have no implementation?)
