06-capabilities

Seed and analyze codebase signals to produce a structured L1/L2 capability map.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/vishalkhondre/unearth --skill 06-capabilities
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 06-capabilities
Source: https://github.com/vishalkhondre/unearth/tree/main/skills/06-capabilities
Command: npx skills add https://github.com/vishalkhondre/unearth --skill 06-capabilities

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seeds and analyzes codebase signals to produce a structured capability map (L1/L2) from recon data and component inventories, enabling architects to understand, plan, and communicate system capabilities.

Core Features & Use Cases

  • Seed capability candidates from upstream recon data, BC inventories, and API endpoints.
  • Analyze candidates for cohesion, boundaries, and dependencies to validate independent capabilities.
  • Produce an auditable L1/L2 capability map with project spans and actor mappings for stakeholder alignment.

Quick Start

Seed and analyze recon data and component inventories to generate the full capability map.

Frequently Asked Questions about 06-capabilities

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map codebase signals into structured business capabilities?

To map codebase signals into capabilities, seed candidates from upstream recon data and component inventories, then analyze them for cohesion and boundaries to produce a structured L1/L2 capability map.

What is a capability map in software architecture?

A capability map in software architecture is an auditable document defining cohesive business capabilities, their boundaries, sub-capabilities, project spans, and actor mappings to align stakeholders on system structure.

How do I identify cohesive business capabilities and their boundaries from a component inventory?

Identify cohesive business capabilities by reading component inventories and entry points, then validate candidates for coupling, dependencies, and coverage to define clear boundaries across multiple projects.

Does codebase capability mapping require upstream recon outputs?

Yes, codebase capability mapping requires upstream recon outputs, component inventories, and API endpoints as seed data to accurately identify business capabilities and verify coverage across the architecture.

What's the best way to verify coverage and cohesion for business capabilities across multiple projects?

The best way to verify capability coverage and cohesion is applying a structured analysis process across multiple projects by reading recon outputs to validate independent capabilities and map actor boundaries.

When should I not use a codebase capability mapping approach?

Avoid codebase capability mapping when upstream recon data, component inventories, or clear entry points are unavailable, as the analysis requires these signals to seed candidates and validate boundaries.