Professional business analysis skill aligned with BABOK® Guide v3 standards. Use this skill when you need to elicit and document requirements, analyze business processes, conduct stakeholder analysis, develop business cases, perform gap analysis, or create business requirements documents (BRD). Ideal for requirements gathering, process mapping (BPMN), financial analysis (ROI, NPV), stakeholder engagement, and solution evaluation. Triggers: "gather requirements", "create business case", "analyze process", "stakeholder analysis", "gap analysis", "BRD", "functional requirements", or requests involving business analysis tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
This skill provides comprehensive business analysis capabilities aligned with the BABOK® (Business Analysis Body of Knowledge) Guide v3 from the International Institute of Business Analysis (IIBA®). It integrates proven methodologies, best practices, and templates to support business analysts in bridging the gap between business needs and technical solutions.
The skill is structured around BABOK's 6 Knowledge Areas:
This skill is designed for both experienced business analysts seeking to standardize their approach and those new to formal business analysis who need structured guidance.
Use this skill when you need to:
Business Analysis Planning and Monitoring
Elicitation and Collaboration
Requirements Life Cycle Management
Strategy Analysis
Requirements Analysis and Design Definition
Solution Evaluation
Use this workflow when gathering requirements from stakeholders.
Determine Elicitation Techniques Based on Context:
Use Interviews When:
Use Workshops When:
Use Surveys When:
Use Observation When:
Use Document Analysis When:
Use Prototyping When:
Create Elicitation Plan:
Objective: [What you want to learn]
Participants:
- [Name/Role] - [Why they're important]
- [Name/Role] - [Why they're important]
Technique: [Interview/Workshop/etc.]
Duration: [Time needed]
Date/Time: [When]
Location: [Where/virtual link]
Agenda:
1. [Topic 1] - [Time allocation]
2. [Topic 2] - [Time allocation]
3. [Topic 3] - [Time allocation]
Questions/Topics:
- [Question 1]
- [Question 2]
- [Question 3]
Interview Question Types:
Open-Ended: "Walk me through your current process for..."
Probing: "Can you tell me more about...?" "Why is that important?"
Closed: "How many orders do you process per day?"
Hypothetical: "If you could change one thing about this process, what would it be?"
Active Listening Techniques:
Document As You Go:
Requirements Categories:
Business Requirements (WHY):
Stakeholder Requirements (WHO needs WHAT):
Functional Requirements (WHAT the solution does):
Non-Functional Requirements (HOW WELL):
Validation Checklist:
Confirmation Methods:
Use Business Requirements Document Template from assets/business_requirements_document_template.md
Key Sections:
Use this workflow to analyze and improve business processes.
Information Gathering:
Key Questions:
Use BPMN (Business Process Model and Notation):
Core Elements:
Create Swimlane Diagram:
┌─────────────┬──────────────────────────────────┐
│ Customer │ ○ → Submit Order → Wait │
├─────────────┼──────────────────────────────────┤
│ Sales │ ← Review → ◇ Approve? │
│ │ ├─[Yes]→ │
│ │ └─[No]→ Reject │
├─────────────┼──────────────────────────────────┤
│ Warehouse │ ← Pick → Ship → ● │
└─────────────┴──────────────────────────────────┘
Document Process Metrics:
Value Stream Mapping - Identify Waste (TIMWOOD):
Process Efficiency Calculation:
Process Efficiency = (Value-Added Time / Total Lead Time) × 100%
Example:
Total Lead Time: 6 days
Value-Added Work: 2 days
Process Efficiency: 2/6 = 33%
Target: Improve to 60%+ efficiency
Common Problem Patterns:
5 Whys Technique:
Problem: High order error rate (15%)
Why? → Data entry mistakes
Why? → Manual entry from paper forms
Why? → No digital order system
Why? → Budget not approved for system
Why? → ROI not demonstrated
Root Cause: Lack of business case
Solution: Develop compelling business case
Fishbone Diagram Categories:
Improvement Strategies:
Eliminate: Remove non-value-added steps
Automate: Use technology to replace manual work
Simplify: Reduce complexity
Integrate: Connect disparate systems
Standardize: Create consistent approach
Future State Design Principles:
Process Improvement Metrics:
Current State → Future State:
Cycle Time: 6 days → 2 days (67% reduction)
Error Rate: 15% → 2% (87% reduction)
Cost/Trans: ¥500 → ¥150 (70% reduction)
Capacity: 500/day → 1,200/day (140% increase)
Annual Benefit Calculation:
- Labor savings: [X] FTE × ¥750,000 = ¥[Amount]
- Error reduction: [X] fewer errors × ¥[Cost] = ¥[Amount]
- Capacity increase: [X] additional revenue = ¥[Amount]
Total Annual Benefit: ¥[Amount]
Use this workflow to identify, analyze, and engage stakeholders effectively.
Brainstorm All Possible Stakeholders:
By Category:
Don't Forget:
Use Stakeholder Analysis Template from assets/stakeholder_analysis_template.md
Power/Interest Matrix:
High Interest
│
Keep │ Manage
Informed │ Closely
│
Low ────────────┼────────────── High
Power │ Power
│
Monitor │ Keep
│ Satisfied
│
Low Interest
Classify Each Stakeholder:
Attitude Assessment:
Tailor Strategy by Stakeholder Type:
For Champions:
For Skeptics:
For Blockers:
Communication Planning:
| Stakeholder | Purpose | Format | Frequency | Message Focus |
|---|---|---|---|---|
| Executive | Decision-making | 1-pager | Monthly | ROI, strategic alignment, risks |
| Project Team | Coordination | Stand-up | Daily | Tasks, blockers, dependencies |
| End Users | Buy-in | Demo | Bi-weekly | WIIFM, ease of use, support |
| IT Ops | Technical alignment | Technical review | Weekly | Architecture, integration, support |
Relationship-Building Techniques:
RACI Matrix: Create clear accountability:
Use this workflow to justify investments and secure funding.
Problem Statement Template:
[Stakeholder group] is facing [problem] which results in [negative impact].
This is caused by [root cause].
If not addressed, [consequence].
Example: "The sales team is facing delays in order processing (average 10 minutes per order) which results in customer dissatisfaction and lost revenue. This is caused by manual data entry into disconnected systems. If not addressed, we will be unable to scale beyond 500 orders/day as business grows."
Quantify Current State:
Generate 3-5 Options:
Option 1: Do Nothing (Baseline)
Option 2-4: Alternative Solutions
Example Options:
For Each Option, Calculate:
Costs:
Benefits:
Financial Metrics:
Use business_analysis.py script:
python scripts/business_analysis.py financial \
--investment 10000000 \
--annual-benefit 3000000 \
--annual-cost 500000 \
--years 3 \
--sensitivity
Weighted Scoring Model:
{
"options": {
"Option A": {"financial": 9, "risk": 6, "strategic_fit": 8, "time": 7},
"Option B": {"financial": 7, "risk": 8, "strategic_fit": 7, "time": 9},
"Option C": {"financial": 5, "risk": 9, "strategic_fit": 6, "time": 8}
},
"weights": {
"financial": 0.4,
"risk": 0.2,
"strategic_fit": 0.3,
"time": 0.1
}
}
Run comparison:
python scripts/business_analysis.py compare options.json
Business Case Structure:
Use Business Case Template from assets/business_case_template.md
Executive Summary (1 page):
Key Sections:
Financial Summary:
Investment: ¥10,000,000
Annual Benefit: ¥3,500,000
Annual Cost: ¥500,000
Net Annual Benefit: ¥3,000,000
Payback Period: 3.3 years
ROI (5 years): 50%
NPV (5 years, 10%): ¥1,350,000
Recommendation: APPROVE
Use this workflow to identify differences between current and desired state.
Assess Current Capabilities:
Example:
Current State: Customer Onboarding
Process: Manual, paper-based, 15 steps
Systems: Excel spreadsheets, email
Capabilities: Can process 20 customers/week
Metrics: 10-day average onboarding time
25% error rate
Customer satisfaction: 6.5/10
Describe Desired State:
Example:
Future State: Customer Onboarding
Process: Automated workflow, 7 steps
Systems: Integrated CRM with digital forms
Capabilities: Can process 100 customers/week
Metrics: 2-day average onboarding time
<5% error rate
Customer satisfaction: 9.0/10
Gap Categories:
Process Gaps:
Technology Gaps:
People/Skills Gaps:
Data Gaps:
Policy/Governance Gaps:
Impact vs. Effort Matrix:
High Impact, Low Effort → Quick Wins (do first)
High Impact, High Effort → Strategic Projects (plan carefully)
Low Impact, Low Effort → Fill-Ins (do if time permits)
Low Impact, High Effort → Time Wasters (avoid or defer)
Gap Prioritization:
| Gap | Impact | Effort | Priority | Dependencies |
|---|---|---|---|---|
| Implement CRM | High | High | 1 | None |
| Digital forms | High | Medium | 2 | CRM integration |
| Training program | Medium | Low | 3 | After CRM go-live |
For Each High-Priority Gap:
Gap: [Description]
Current State: [What exists today]
Future State: [What's needed]
Actions to Close Gap:
1. [Action 1] - Owner: [Name] - By: [Date] - Cost: ¥[Amount]
2. [Action 2] - Owner: [Name] - By: [Date] - Cost: ¥[Amount]
3. [Action 3] - Owner: [Name] - By: [Date] - Cost: ¥[Amount]
Success Criteria: [How to measure gap is closed]
Timeline: [Start] to [End]
Total Cost: ¥[Amount]
Traceability Matrix:
Business Need → Business Req → Functional Req → Design → Test Case → Deployment
Example:
Business Need: "Improve customer service"
└─ BR-001: "Reduce response time"
└─ FR-015: "Auto-route tickets by category"
└─ Design-03: "Routing rules engine"
└─ TC-087: "Verify routing accuracy"
└─ Release 2.1: "Deployed 2025-03-15"
Benefits:
User Stories Format:
As a [role],
I want [capability],
So that [benefit].
Acceptance Criteria:
- Given [precondition]
- When [action]
- Then [expected result]
Example:
As a sales representative,
I want to access customer order history from my mobile device,
So that I can answer customer questions during site visits.
Acceptance Criteria:
- Given I'm logged in on mobile app
- When I search for a customer
- Then I see their complete order history within 2 seconds
- And I can filter by date range
- And I can view order details
Story Mapping:
Use business_analysis.py for data profiling:
python scripts/business_analysis.py profile sales_data.csv --output profile_report.json
Analysis Techniques:
Trend Analysis:
Segmentation:
Comparative Analysis:
Resolution Process:
Facilitate Requirements Workshop
Apply MoSCoW Prioritization
Escalate to Decision Maker
Implement Change Control
Use Prototypes
Fast-Track Approach:
Problem Statement (30 min)
Solution Options (1 hour)
Financial Analysis (30 min)
Risk Assessment (30 min)
Recommendation (30 min)
Total Time: 3 hours for initial business case
Systematic Approach:
Map Current Process (As-Is)
Collect Metrics
Identify Pain Points
Root Cause Analysis
Design Future State
Prioritization Frameworks:
MoSCoW:
Value vs. Complexity:
High Value + Low Complexity = Do First
High Value + High Complexity = Phase 2 (plan carefully)
Low Value + Low Complexity = Nice to have
Low Value + High Complexity = Don't do
Kano Model:
Forced Ranking:
babok_framework.md Comprehensive guide to BABOK® Guide v3 with all 6 knowledge areas. Covers business analysis planning, elicitation techniques, requirements management, strategy analysis, requirements analysis, and solution evaluation. Use this as your primary BA methodology reference.
process_data_analysis.md Detailed guide to process analysis techniques (BPMN, value stream mapping, gap analysis, root cause analysis) and data analysis methods (data profiling, data quality, BI reporting, segmentation). Use this for process improvement and data-driven analysis.
business_requirements_document_template.md Comprehensive BRD template following industry standards. Includes business problem, objectives, scope, stakeholder analysis, current/future state, requirements detail, business rules, and acceptance criteria. Use this for documenting requirements.
business_case_template.md Professional business case template with financial analysis, risk assessment, options comparison, and recommendation sections. Includes ROI, NPV, payback period calculations. Use this to justify investments and secure funding.
stakeholder_analysis_template.md Complete stakeholder analysis framework with power/interest matrix, engagement strategies, communication planning, and RACI matrix. Use this for identifying and managing stakeholders throughout project lifecycle.
business_analysis.py Python toolkit for business analysis tasks:
Usage Examples:
# Financial analysis with sensitivity
python scripts/business_analysis.py financial \
--investment 10000000 \
--annual-benefit 3000000 \
--years 3 \
--sensitivity
# Profile dataset
python scripts/business_analysis.py profile sales_data.csv --output report.json
# Compare options
python scripts/business_analysis.py compare options.json
✓ Use multiple elicitation techniques ✓ Involve diverse stakeholders ✓ Ask open-ended questions ✓ Listen actively without bias ✓ Confirm understanding continuously ✓ Document requirements immediately ✓ Distinguish needs from solutions
✓ Write clear, unambiguous requirements ✓ Make requirements testable ✓ Maintain traceability ✓ Use consistent templates ✓ Version control all documents ✓ Get formal sign-off ✓ Keep requirements up to date
✓ Identify stakeholders early and comprehensively ✓ Understand motivations and concerns ✓ Communicate proactively ✓ Tailor communication style ✓ Build trust through transparency ✓ Manage expectations realistically ✓ Document commitments
✓ Map current state first (as-is) ✓ Involve process participants ✓ Quantify current metrics ✓ Identify root causes, not symptoms ✓ Design future state with stakeholders ✓ Quantify expected benefits ✓ Plan for change management
✓ Quantify problem impact ✓ Develop multiple options ✓ Calculate financial metrics (ROI, NPV, Payback) ✓ Assess risks and mitigation ✓ Include sensitivity analysis ✓ Present clear recommendation ✓ Define success metrics
✓ Use standard notations (BPMN, UML) ✓ Keep models simple and focused ✓ Validate models with stakeholders ✓ Use appropriate level of detail ✓ Update models as requirements evolve
Root Causes:
Solutions:
Root Causes:
Solutions:
Root Causes:
Solutions:
Common Reasons:
Recovery Actions:
Project Context:
How This Skill Helps:
Requirements Elicitation (Workflow 1)
Stakeholder Analysis (Workflow 3)
Business Case (Workflow 4)
Outcome:
Project Context:
How This Skill Helps:
Process Analysis (Workflow 2)
Gap Analysis (Workflow 5)
Business Case (Workflow 4)
Outcome:
This Business Analyst skill provides comprehensive capabilities aligned with BABOK® Guide v3 standards. By following structured workflows for requirements elicitation, process analysis, stakeholder management, business case development, and gap analysis, you can deliver high-quality business analysis that bridges the gap between business needs and technical solutions.
Key Takeaways:
Next Steps:
Remember: "The value of business analysis isn't in creating perfect documents, but in facilitating shared understanding and enabling informed decisions."
Business analysis is fundamentally about communication, collaboration, and clarity - helping organizations make better decisions through structured thinking and stakeholder engagement.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Track and update action item status from natural language updates like 'Seanのメールには返信しておいた' or 'Lu対応予定'. Integrates with daily-comms-ops workflow. Use when managing action items across communication channels.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI活用提案の専門コンサルタントスキル。LLM・AIエージェントの活用事例知識を基に、業界別、部門別、シーン別に最適なAI導入提案を行います。システム化、業務改善、効率化を得意とし、具体的な活用事例、期待効果、導入ステップを含む実践的な提案を提供します。Use when proposing AI/LLM adoption strategies for specific industries, departments, or business scenarios.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate AI-powered BPO service proposals for Japanese companies in the US market. Use when creating outsourcing proposals with AI service menus, ROI estimation, implementation roadmaps, and bilingual (JA/EN) proposal documents for 在米日系企業向けAI実装.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI（LLM）が生成した日本語テキストの「AI臭」を検出・診断し、人間らしい文章にリライトするスキル。 Use when: 「AIっぽい文章を直して」「人間らしくリライトして」「AI臭を消して」「この文章をもっと自然にして」 「テキストのAI感を減らして」「機械っぽさを取りたい」 "make this sound more human", "remove AI tone", "humanize this text", "detect if this is AI-generated". 6つのAI特有パターン（視覚的マーカー、単調なリズム、マニュアル的構成、非コミット姿勢、抽象語の濫用、 定型メタファー）を正規表現ベースで検出し、0-100のAI臭スコアを算出。3つの人間化技法 （バランスを崩す・客観を崩す・論理を崩す）でリライトを実行する。 Note: 検出スクリプトは日本語テキスト専用。英語テキストの場合はClaude自身がreferences/を参照して分析・リライトする。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate audit-ready internal control design documents from As-Is business process inventories. Produces control IDs, assertion mappings, procedures, SoD analysis, KPIs, materiality thresholds, and implementation roadmaps. Use when building internal controls for new audit engagements, SOX/J-SOX compliance, or process improvement initiatives.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review audit-related documents (control design documents, bottleneck analyses, requirements definitions, etc.) for quality, scoring them 0-100 with a severity-rated findings list. Use when reviewing audit documents, checking control design quality, or verifying cross-document consistency. Supports documents governed by US GAAP, IFRS, or J-GAAP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.