Business capability modeling using BABOK Business Capability Analysis. Creates hierarchical capability maps (L1-L3) linking strategy to architecture with Mermaid visualization.
Creates hierarchical business capability maps (L1-L3) linking strategy to architecture using BABOK analysis. Triggers when analyzing business domains, planning digital transformation, or mapping processes to strategic capabilities for investment prioritization.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install business-analysis@melodic-softwareThis skill is limited to using the following tools:
references/capability-hierarchy.mdCreate hierarchical business capability models that bridge strategy and architecture. Based on BABOK v3 Business Capability Analysis (10.6).
A business capability defines "what" a business does at its core, independent of:
Capabilities are stable over time, even as processes, technology, and org structure change.
| Level | Scope | Example | Description |
|---|---|---|---|
| L1 | Domain | Customer Management | Strategic capability areas (typically 8-15) |
| L2 | Sub-Domain | Customer Onboarding | Decomposition of L1 (3-7 per L1) |
| L3 | Activity | Identity Verification | Detailed activities (3-10 per L2) |
| L4+ | Optional | KYC Document Processing | Granular (map to SOA services) |
| Type | Description | Investment Priority |
|---|---|---|
| Strategic | Drive competitive advantage | High - differentiate |
| Core | Essential to value delivery | Medium - optimize |
| Supporting | Enable other capabilities | Low - commoditize/outsource |
Before creating a capability map, understand the business domain:
Analyze existing documentation
Conduct stakeholder interviews
stakeholder-analysis skill to identify key stakeholdersUse discovered patterns as L1 capability candidates
Start with industry frameworks, then customize:
## L1 Capabilities (Example: Retail)
| # | Capability | Type | Description |
|---|------------|------|-------------|
| 1 | Product Management | Core | Manage product lifecycle |
| 2 | Customer Management | Core | Manage customer relationships |
| 3 | Order Fulfillment | Core | Process and deliver orders |
| 4 | Supply Chain | Core | Manage suppliers and inventory |
| 5 | Finance & Accounting | Supporting | Financial operations |
| 6 | Human Resources | Supporting | People management |
| 7 | IT Services | Supporting | Technology operations |
| 8 | Marketing | Strategic | Brand and customer acquisition |
For each L1, identify sub-capabilities:
## L2 Decomposition: Customer Management
| L2 Capability | Owner | Maturity | Systems |
|---------------|-------|----------|---------|
| Customer Onboarding | Customer Success | 3 | CRM, KYC |
| Customer Support | Support Team | 4 | Ticketing, Chat |
| Customer Retention | Marketing | 2 | CRM, Analytics |
| Customer Analytics | Data Team | 2 | BI Platform |
Only decompose where detail is needed for planning:
## L3 Decomposition: Customer Onboarding
| L3 Capability | Description | Status |
|---------------|-------------|--------|
| Identity Verification | Verify customer identity | Automated |
| Account Creation | Create customer account | Automated |
| KYC Processing | Know Your Customer compliance | Semi-manual |
| Welcome Communication | Onboarding emails/guides | Automated |
Map capabilities to other domains for strategic analysis:
| Cross-Map Domain | Purpose | Example Questions |
|---|---|---|
| People | Ownership | Who owns this capability? |
| Process | Execution | What processes implement this? |
| Technology | Enablement | What systems support this? |
| Strategy | Alignment | How does this support strategy? |
| Investment | Prioritization | Where should we invest? |
| Risk | Exposure | What are the risks? |
Score each capability on maturity and strategic importance:
Maturity Scale (1-5):
Heat Map Visualization:
## Capability Heat Map
| Capability | Maturity | Importance | Gap | Action |
|------------|----------|------------|-----|--------|
| Customer Onboarding | 3 | High | Low | Maintain |
| Customer Analytics | 2 | High | High | Invest |
| IT Services | 4 | Medium | Low | Maintain |
| HR Admin | 3 | Low | Low | Outsource? |
Provide human-readable analysis:
## Capability Map Summary
**Organization:** [Name]
**Scope:** [Enterprise / Business Unit / Domain]
**Date:** [ISO date]
### Key Findings
1. **Strategic Capabilities:** [List with assessment]
2. **Investment Priorities:** [Capabilities needing attention]
3. **Optimization Opportunities:** [Capabilities to streamline]
### Recommendations
1. [Specific, actionable recommendation]
2. [...]
capability_model:
version: "1.0"
organization: "Acme Corp"
scope: enterprise
generated: "{ISO-8601-date}"
generated_by: capability-analyst
capabilities:
- id: CAP-001
name: "Customer Management"
level: 1
type: core
description: "Manage customer lifecycle and relationships"
owner: "Chief Customer Officer"
children:
- id: CAP-001-01
name: "Customer Onboarding"
level: 2
owner: "Customer Success Director"
maturity: 3
importance: high
systems:
- CRM
- KYC Platform
processes:
- "Customer Registration"
- "Identity Verification"
children:
- id: CAP-001-01-01
name: "Identity Verification"
level: 3
maturity: 4
automation: high
mindmap
root((Enterprise))
Customer Management
Customer Onboarding
Identity Verification
Account Creation
KYC Processing
Customer Support
Ticket Management
Live Chat
Customer Retention
Product Management
Product Catalog
Pricing
Promotions
Order Fulfillment
Order Processing
Shipping
Returns
| Scenario | Use Capability Mapping? |
|---|---|
| Strategic planning | Yes - align investments |
| M&A integration | Yes - identify overlaps |
| Digital transformation | Yes - prioritize initiatives |
| Application rationalization | Yes - map apps to capabilities |
| Process improvement | Partial - use with process modeling |
| Specific feature design | No - too high-level |
references/capability-hierarchy.md for detailed hierarchy guidancestakeholder-analysis - Identify capability ownersvalue-stream-mapping - Map value flow across capabilitiesbenchmarking - Compare capability maturity against industry standardsprioritization - Prioritize capability investmentsswot-pestle-analysis - Strategic context for capabilitiesdecision-analysis - Evaluate capability investment optionsUse when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.