Three slash commands

The BA Skills Library

Each skill encodes a methodology — not just a prompt. Guided elicitation, validation checkpoints, interactive output, and export for the VCC pipeline.

Skill 1 of 3

BA Capability Mapping

/capability-map

Produces a MECE (Mutually Exclusive, Collectively Exhaustive) capability hierarchy grounded in the Business Architecture Guild's BIZBOK framework. The skill elicits L1 Business Areas and L2 Business Domains first, pauses for your validation, then derives L3 Business Capabilities from confirmed foundations.

Execution and Governance capabilities are distinguished throughout. The output is structurally correct — not just formatted — because the methodology is embedded in the skill.

What it produces

  • Interactive treemap — L1 containers, L2 groups, L3 hoverable tiles. Execution in blue, Governance in purple.
  • XLSX workbook — Summary, Capability Register, Validation, Legend tabs
  • JSON export — capabilities section of the ba-skills-bundle.json

Validation checkpoints

Checkpoint 1 — L1/L2 hierarchy presented for recognition. The naming convention and structure must feel right before L3 is derived.

Checkpoint 2 — Full L1–L3 map reviewed. Capabilities must feel like stable organisational abilities, not process steps or system names.

Quality bars
MECE hierarchy
No overlapping siblings. No exhaustiveness gaps. Every L3 belongs unambiguously to one L2.
Verb–Noun naming
Every L3 capability named as "Manage X", "Track X", "Define X" — stable abilities, not activities.
Business object grounding
Every capability references a named business object. Objects without capabilities signal a gap.
Typical output
6–10 L1 domains · 15–30 L2 groups · 40–120 L3 capabilities depending on scope.
Install and run /capability-map →
Skill 2 of 3

BA Concept Model

/concept-model

Produces a business object taxonomy using the Capsicum Triad — Party, Record, Resource — grounded in REA theory (McCarthy 1982) and Bunge's ontology. Every object is defined, typed, given lifecycle states, and related to at least one capability.

Run in the same session as /capability-map and the concept model will cross-validate both ways — every object should ground at least one capability, and every capability should reference a named object. Gaps surface immediately.

The Capsicum Triad

Party — a person or organisation that plays a role (Owner, Guest, Contractor)
Resource — a thing of value that is managed, exchanged, or consumed (Property, Booking, Tenancy)
Record — a document that captures evidence of something that happened (Financial Report, Guest Review)

What it produces

  • Interactive concept graph — typed nodes with edges. Click any node for definition and lifecycle states.
  • XLSX workbook — Object Register, Relationships, Validation, Legend tabs
  • JSON export — concepts section of the ba-skills-bundle.json
Quality bars
8–20 objects
Fewer suggests under-modelling. More suggests conflation of objects at different levels of abstraction.
Every object grounded
Every object references at least one L3 capability. Objects with no capabilities are candidates for removal.
Lifecycle states
Every object has at least one lifecycle state sequence. States reveal the business events that matter.
Install and run /concept-model →
Skill 3 of 3

BA Value Streams

/value-stream

Maps how an organisation delivers value to a recipient through a sequence of stages — each with named entry and exit outcomes, accountable stakeholders, required capabilities, and a PPIT breakdown (People, Process, Information, Technology).

The value stream is the thread that ties capability map and concept model together. Every stage requires capabilities from the map; every capability references objects from the concept model. The three skills form a coherent, cross-validated operating model.

What it produces

  • Interactive stage view — outcome chain, stage cards with PPIT dots, click-through inspector panel per stage
  • XLSX workbook — Stage Register, Capability Mapping, Validation, Legend tabs
  • ba-skills-bundle.json — complete schema-validated bundle for VCC pipeline import

VCC pipeline

The ba-skills-bundle.json imports directly into the Value Cognition Canvas, where it becomes the foundation for friction analysis, solution mapping, throughput projections, and governance controls.

Quality bars
4–8 stages
Fewer suggests conflation. More suggests process-level mapping rather than value-stage thinking.
Outcome chain
Every stage has named entry and exit criteria. Exit of one stage must equal entry of the next.
No orphan stages
Every stage requires at least one L3 capability. Stages with no capabilities signal a gap in the map.
Install and run /value-stream →

Run all three in sequence

A complete operating model slice — capability map, concept model, and value stream — cross-validated and pipeline-ready. One Cowork session.

Install free in Cowork → Read the methodology