PlausibleBA — BA Skills for Claude

Just enough business architecture. For every BA, on every project.

PlausibleBA gives business analysts the business architecture techniques they need to ground their work — capability mapping, concept modelling, value stream design — without requiring a business architecture practice or a BIZBOK certification.

Each skill encodes a proven methodology, walks you through it step by step, and produces a professional artefact your stakeholders will recognise. The result is architecture-quality thinking delivered at BA speed.

---

Why business architecture for BAs?

Business architects have a toolkit that BAs have largely left on the table: capability maps that ground requirements in what the organisation actually does, concept models that eliminate ambiguity about what terms mean, value streams that show how capabilities orchestrate to deliver outcomes.

These aren’t enterprise architecture exercises. Used at project scope, they make every other BA technique more rigorous — stakeholder analysis, requirements elicitation, gap analysis, solution design. PlausibleBA makes them accessible.

---

Installation

One plugin, PlausibleBA — Business Architecture Skills, installs all six skills.

Claude (claude.ai and Cowork)

1. Go to Customize → Plugins and choose + Add
2. Add the marketplace from GitHub: plausibleba/ba-skills
3. Add PlausibleBA — Business Architecture Skills

Claude Code (CLI)

claude plugin marketplace add plausibleba/ba-skills
claude plugin install plausible-ba@plausible-ba

Run a skill by asking for what it does (“prepare a context document for …”, “build a capability map from these notes”) or by name, for example /ba-opmodel-context.

Other AI assistants

The skills/*/SKILL.md files follow the universal skill format and work with any tool that supports skill files.

---

Available skills

ba-opmodel-context — v1.0.0 (first run September 2026)

Know what can be known before you ask. Build a Context Document for an organisation and the division in scope from public and supplied material — annual reports, regulator and industry standards, statistics agencies, trade press, the customer’s own documents — with every line marked EVIDENCED, INFERRED or ASSUMED and sourced. Written for the customer to correct before any model is built.

Run it: /ba-opmodel-context

What you get:

• Fourteen sections, each mapped to the PlausibleBA door it feeds — source register, organisation frame, operating landscape, roles, candidate value streams, reference capability map, concept model, technology, governance, directives, metrics, friction signals, known unknowns, readiness
• The industry standard as the spine (IOSA, IGOM/AHM, A-CDM and AIDM for airlines; a table that grows one sector at a time)
• Known unknowns paired with the customer document that would settle each one