capability-map

Create business capability maps classifying L1-L3 capabilities and overlaying systems and investments.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula --skill capability-map-serpro-workshop-fortaleza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capability-map
Source: https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula/tree/main/.github/skills/capability-map
Command: npx skills add https://github.com/serpro-workshop-fortaleza/sifap-modernization-paula --skill capability-map-serpro-workshop-fortaleza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to see what the business actually does versus how systems support it, leading to duplicated applications, unowned capabilities, and misaligned IT investment. This Skill structures that analysis into a three-level capability map with clear ownership and classification. ## Core Features & Use Cases - Three-Level Decomposition: Breaks the business into L1 areas, L2 sub-functions, and L3 evidence-backed capabilities, stopping when each capability has a single accountable owner. - Classification and Overlay: Tags each L3 capability as Core, Supporting, or Commodity, then overlays systems and investment to expose duplication, gaps, and monoliths. - Use Case: An enterprise architect asks where two teams overlap. The Skill produces a Mermaid diagram and a Markdown template listing each L3 capability with its owner, systems, maturity score, and investment level. ## Quick Start Create a capability map for the domain my team identified, classifying each capability as Core, Supporting, or Commodity and flagging duplicated systems.

Frequently Asked Questions about capability-map

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

FAQPage Schema
How do I create a business capability map?

Start from business outcomes rather than the org chart, then decompose top-down into L1 areas, L2 sub-functions, and L3 capabilities. Stop decomposing when each capability maps to exactly one accountable owner, typically 8-12 L1 capabilities for a mid-size company.

What is the difference between a capability and a process?

A capability describes what the business does, not how it does it. Capabilities remain stable for decades while applications and processes change frequently, which makes them a durable basis for architecture and investment decisions.

How do I classify capabilities as Core, Supporting, or Commodity?

Classify Core capabilities as differentiators to build in-house, Supporting capabilities as necessary functions to buy or configure, and Commodity capabilities as undifferentiated work to outsource or cover with SaaS. Apply the classification at the L3 level.

How do I find duplicate systems with a capability map?

Overlay each L3 capability with the applications that deliver it. Two systems serving the same capability indicate duplication, a capability with no system indicates a gap, and one system spanning many L1 areas indicates a monolith.

When should I stop decomposing capabilities into lower levels?

Stop at L3 when a capability corresponds to a single accountable owner. Decomposing further creates task-level detail that belongs in process documentation rather than a capability map.