Use this skill whenever a business analyst, architect, or project team needs to produce a Capability Map — even if they don't use that exact term. Trigger on phrases like: "map out what the business does", "identify our capabilities", "build a capability model", "what capabilities do we need for this initiative", "capability assessment", "business capability map", "organisational abilities", or when someone uploads a project charter, discovery transcript, existing Excel capability model, or industry reference model and asks for structured analysis. Also trigger when someone wants to prepare for a VCC (Value Cognition Canvas) session or asks what capabilities a value stream requires. The skill handles any input format — raw transcripts, structured documents, Excel files, or verbal descriptions.
Use this skill whenever a business analyst, architect, or project team needs to identify, define, and structure the core business objects (concepts) of a domain — even if they don't use that exact term. Trigger on phrases like: "what are the key things the business manages", "define our business objects", "build a concept model", "what data entities do we need", "domain model", "business glossary", "core concepts", "object model", or when someone wants to understand what a business manages before designing systems, processes, or value streams. Also trigger when a Capability Map has been produced and the user wants to validate coverage through the objects that ground the capabilities, or when preparing for a VCC session. The skill handles any input — transcripts, charters, existing capability maps, or verbal descriptions. Always load ba-taxonomy-standard alongside this skill.
Use this skill when someone wants to run a complete business architecture session — producing a Capability Map, Concept Model, and Value Stream in one guided flow. Trigger on phrases like: "run PlausibleBA", "build my business architecture", "I want a full BA model", "run all three", or when someone invokes /plausibleba. This skill orchestrates the three individual skills in sequence and packages the result into a single ba-skills-bundle.json for VCC import.
Use this skill whenever a business analyst, architect, or project team needs to identify, map, or analyse value streams — even if they don't use that term. Trigger on phrases like: "map out how we deliver value", "end-to-end process", "customer journey from our side", "how does a booking become a completed stay", "what stages does X go through", "value stream map", "flow of value", "lifecycle stages", or when someone wants to understand how capabilities orchestrate to deliver an outcome. Also trigger when a Capability Map and Concept Model exist and the user wants to validate them by tracing a value stream through both. The skill handles any input — transcripts, charters, existing process maps, swim lane diagrams described in text, or verbal descriptions. Always load ba-taxonomy-standard alongside this skill.
Shared conventions used across all PlausibleBA skills. Load this skill whenever producing, validating, or comparing any PlausibleBA taxonomy — Capability Maps, Concept Models, Value Streams, or any other structured artefact. It defines the numbering system, column order, naming conventions, MECE rules, and XLSX formatting standards that keep all outputs consistent and cross-referenceable.