{
  "markdown": "# PlausibleBA — BA Skills for Claude\n\n**Just enough business architecture. For every BA, on every project.**\n\nPlausibleBA gives business analysts the business architecture techniques they need\nto ground their work — capability mapping, concept modelling, value stream design —\nwithout requiring a business architecture practice or a BIZBOK certification.\n\nEach skill encodes a proven methodology, walks you through it step by step, and\nproduces a professional artefact your stakeholders will recognise. The result is\narchitecture-quality thinking delivered at BA speed.\n\n---\n\n## Why business architecture for BAs?\n\nBusiness architects have a toolkit that BAs have largely left on the table:\ncapability maps that ground requirements in what the organisation actually does,\nconcept models that eliminate ambiguity about what terms mean, value streams that\nshow how capabilities orchestrate to deliver outcomes.\n\nThese aren't enterprise architecture exercises. Used at project scope, they make\nevery other BA technique more rigorous — stakeholder analysis, requirements\nelicitation, gap analysis, solution design. PlausibleBA makes them accessible.\n\n---\n\n## Installation\n\n### Claude Cowork (recommended)\n\n1. Open Cowork → Plugins → Browse → Personal → **+**\n2. Select **Add marketplace from GitHub**\n3. Enter: `plausibleba/ba-skills`\n4. Install the plugins you need\n\n### Claude Code (CLI)\n\n```bash\nclaude plugin marketplace add plausibleba/ba-skills\nclaude plugin install ba-capability-mapping@ba-skills\nclaude plugin install ba-concept-model@ba-skills\nclaude plugin install ba-value-streams@ba-skills\n```\n\n### Other AI assistants\n\nThe `skills/*/SKILL.md` files follow the universal skill format and work with any\ntool that supports skill files. The `/slash-commands` are Claude-specific.\n\n---\n\n## Available skills\n\n### `ba-capability-mapping` — v1.0.0 ✅\n\nMap what the business can do. Produce a MECE, investment-relevant capability map\nfrom any input — transcripts, charters, existing spreadsheets, or industry reference\nmodels. Grounded in BIZBOK principles and validated against BABOK technique standards.\n\n**Command:** `/capability-map`\n\n**What you get:**\n- Two-checkpoint elicitation: L1/L2 confirmed before L3 derivation\n- MECE validation at every level with Execution/Governance split\n- Hierarchical numbering (`1.2.3`) — sort column A to see the full structure\n- 4-tab XLSX: Summary, Capability Register, Validation, Legend\n- JSON for VCC pipeline integration\n\n**Example output:** [`examples/portfolioprop_capability_map_v2.xlsx`](examples/portfolioprop_capability_map_v2.xlsx)\n\n---\n\n### `ba-concept-model` — v1.0.0 ✅\n\nName and define the things the business manages. Produce a typed taxonomy of core\nbusiness objects — cross-validated against the Capability Map to confirm every\ncapability is grounded and every object is covered.\n\nUses the **Capsicum Triad** (Party / Record / Resource) — a principled three-type\nclassification consistent with REA (McCarthy 1982) and Bunge's ontology for\ninformation systems. A custom hierarchy option is also offered.\n\n**Command:** `/concept-model`\n\n**What you get:**\n- Classification Checkpoint: choose Capsicum Triad or custom hierarchy\n- Object Register with type, definition, lifecycle states, and related capabilities\n- Cross-validation: object ↔ capability coverage confirmed both directions\n- 4-tab XLSX: Summary, Object Register, Validation, Legend\n- JSON for VCC pipeline integration\n\n**Example output:** [`examples/portfolioprop_concept_model_v1.xlsx`](examples/portfolioprop_concept_model_v1.xlsx)\n\n---\n\n### `ba-value-streams` — v1.0.0 ✅\n\nMap how the business delivers value. Decompose a value stream into 4–8 stages,\neach with entry/exit criteria, participating capabilities, and business objects in\nplay. Cross-validates both the Capability Map and Concept Model.\n\n**Command:** `/value-stream`\n\n**What you get:**\n- Recipient-centric stage naming (state reached, not activity performed)\n- Entry/exit criteria at every stage\n- Capability cross-reference: unused capabilities flagged, gaps identified\n- Layout zone assignment for VCC network view (auto-inferred from Recipient type)\n- 4-tab XLSX: Summary, Stage Register, Validation, Legend\n- `ba-skills-bundle.json` for VCC import\n\n**Example output:** [`examples/portfolioprop_value_stream_v1.xlsx`](examples/portfolioprop_value_stream_v1.xlsx)\n\n---\n\n## The full pipeline\n\nRun all three skills in sequence on the same engagement and you get a complete,\ncross-validated operating model slice:\n\n```\n/capability-map    What the organisation can do\n      ↓\n/concept-model     What the organisation manages\n      ↓\n/value-stream      How the organisation delivers value\n      ↓\nba-skills-bundle.json   →   VCC session\n```\n\nThe `ba-skills-bundle.json` is the handoff to the\n[Value Cognition Canvas](https://www.plausibleba.com/vcc) — a facilitated session\ntool for operating model assessment, friction identification, and investment\nprioritisation.\n\n**Example bundle:** [`examples/portfolioprop_ba-skills-bundle_v1.json`](examples/portfolioprop_ba-skills-bundle_v1.json)\n\n---\n\n## The PlausibleBA Taxonomy Standard\n\nAll skills share a common standard ensuring artefacts from the same engagement\nfit together:\n\n- **Numbering:** `1.2.3` positional format; sort by Number to see the hierarchy\n- **Column order:** consistent across all XLSX outputs\n- **MECE:** mutually exclusive and collectively exhaustive at every level\n- **Cross-taxonomy traceability:** Business Objects as the shared thread\n- **Branding:** consistent PlausibleBA header on all XLSX outputs\n\nSee [`ba-capability-mapping/skills/ba-taxonomy-standard/SKILL.md`](ba-capability-mapping/skills/ba-taxonomy-standard/SKILL.md)\n\n---\n\n## Coming next\n\n| Skill | What it answers | Status |\n|-------|----------------|--------|\n| `ba-ppit-mapping` | How well do we do it? (People/Process/Information/Technology) | In development |\n| `ba-requirements` | What do we need to change? | Planned |\n| `ba-stakeholder-analysis` | Who is affected and how? | Planned |\n\n---\n\n## About\n\nPlausibleBA is built on the [Capsicum Framework](https://www.plausibleba.com) —\na formal approach to business architecture grounded in real delivery experience.\nThe skills encode practitioner judgment: not just what to produce, but how to\nthink through it.\n\nThe name is intentional. *Plausible BA* — the business analyst who does just enough\narchitecture to make the work rigorous. *Plausible Business Architecture* — formal\nenough to be defensible, accessible enough to be used on any project.\n\nQuestions, issues, contributions: [open an issue](https://github.com/plausibleba/ba-skills/issues).\n\n---\n\n*Generated by the PlausibleBA Skills Library | [www.plausibleba.com](https://www.plausibleba.com)*\n",
  "bytes": 6725,
  "sha": "267bc57ef90eb04b72c958dd0657613d6fd4abe695b84a158c4cd7abd0ecda46",
  "repo_slug": "plausibleba/ba-skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_plausibleba_ba_skills_plausibleba_busine_3a9aba12/readme"
}