From profile-playbook
This skill should be used when the user asks to "analyze business requirements", "do business analysis", "create a requirements document", "map business processes", "write user stories", "feasibility assessment", "stakeholder analysis", "data modelling", "process improvement", "acceptance criteria", "business case", "gap analysis", "as-is to-be analysis", "business modelling", "requirements elicitation", "impact analysis", or mentions business analyst / business analysis work. Guides developers, analysts and aspiring BAs through business analysis tasks using SFIA 9 framework with a 5-phase workflow (Discover → Define → Analyze → Design → Deliver & Validate), inline coaching, and competency assessment. Do NOT use for: solution architecture, infrastructure design, product roadmap management, or code-level implementation decisions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/profile-playbook:ba-playbookThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guides developers, analysts and aspiring BAs through Business Analysis tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build BA competency from SFIA level 4 (Enable) toward level 5-6.
Guides developers, analysts and aspiring BAs through Business Analysis tasks using the SFIA 9 framework. Combines a phase-based workflow with inline coaching to build BA competency from SFIA level 4 (Enable) toward level 5-6.
| # | Phase | Purpose | Key SFIA Skills | Key Artifacts |
|---|---|---|---|---|
| 1 | Discover | Investigate business situation, stakeholders, current state | BUSA, RLMT | Stakeholder map, Problem statement, As-is analysis |
| 2 | Define | Formalize requirements, scope, feasibility | REQM, FEAS, BSMO | Requirements doc, Business model, Feasibility assessment |
| 3 | Analyze | Improve processes, model data, analyze UX | BPRE, DTAN, UNAN | Process maps, Data model, UX analysis |
| 4 | Design | Select methods, design solution, define acceptance | METL, BPTS, STPL | Solution options, Acceptance criteria, Methods selection |
| 5 | Deliver & Validate | Test, handoff, manage change | BPTS, CNSL, CIPM | Test plan, Handoff package, Change impact assessment |
For detailed phase activities, coaching prompts, and artifact guidance, consult references/ba-phases.md.
When the user initiates a BA task:
BA-{PROJECT}-{YYYYMMDD}-{SEQ} (derive PROJECT from directory name).ba-playbook/sessions/{session_id}/state.yaml with phase trackingsession_id: BA-{PROJECT}-{YYYYMMDD}-{SEQ}
current_phase: discover
phases:
discover: { status: in_progress, artifacts: [] }
define: { status: not_started, artifacts: [] }
analyze: { status: not_started, artifacts: [] }
design: { status: not_started, artifacts: [] }
deliver_validate: { status: not_started, artifacts: [] }
coaching_log: []
.ba-playbook/sessions/{session_id}/
├── state.yaml
├── discover/
├── define/
├── analyze/
├── design/
└── deliver-validate/
state.yaml to continue where left offAt key moments (artifact completion, analysis decisions, phase transitions), provide coaching:
> **BA Coach** (REQM L4 → L5)
> [Observation about current work]
> [Tip for next-level performance]
Coaching guidelines:
For coaching prompt templates by skill and level, consult references/coaching-prompts.md.
When reviewing BA work (via /ba:assess or during a session):
For the full assessment rubric, consult references/assessment-criteria.md.
The primary SFIA skills for BA work and their phase mapping:
| Skill | Code | Primary Phases |
|---|---|---|
| Business situation analysis | BUSA | Discover |
| Feasibility assessment | FEAS | Define |
| Requirements definition | REQM | Define, all phases |
| Methods and tools | METL | Design, all phases |
| Business process improvement | BPRE | Analyze |
| Data modelling and design | DTAN | Analyze |
| Acceptance testing | BPTS | Design, Deliver & Validate |
| User experience analysis | UNAN | Analyze |
| Business modelling | BSMO | Define |
For full SFIA skill descriptions at each level, consult references/sfia-skill-map.md.
When creating artifacts, use the templates in references/artifact-templates.md. Templates include:
When selecting business analysis approaches, consult references/ba-patterns.md for common patterns with trade-off analysis:
Target audience: Dev/Analyst → BA (SFIA Level 4), with growth path:
references/ba-phases.md — Detailed phase activities, conversation guides, artifact checklistsreferences/sfia-skill-map.md — Full SFIA skill descriptions for BA-relevant skills at each levelreferences/coaching-prompts.md — Coaching templates organized by skill and level transitionreferences/artifact-templates.md — Ready-to-use templates for all BA artifactsreferences/assessment-criteria.md — Full rubric for BA competency assessment scoringreferences/ba-patterns.md — Common business analysis patterns with trade-off analysisnpx claudepluginhub baodq97/open-plugin --plugin profile-playbookOrchestrates 14 BABOK techniques for strategic analysis, problem solving, planning, estimation, and process/data design into goal-specific analysis packages.
Conducts structured business analyses for project backlog items: problem/stakeholder analysis, as-is/to-be gap analysis, user personas, scope definition. Creates BA documents using EXPLORATION/IDEATION/VALIDATION phases.