faion-business-analyst
11
总安装量
10
周安装量
#27130
全站排名
安装命令
npx skills add https://github.com/faionfaion/faion-network --skill faion-business-analyst
Agent 安装分布
claude-code
7
github-copilot
6
codex
6
gemini-cli
5
antigravity
5
Skill 文档
Entry point:
/faion-netâ invoke this skill for automatic routing to the appropriate domain.
BA Domain Skill
Orchestrator for Business Analysis Framework (BABOK) practices
Context Discovery
Auto-Investigation
Check for existing BA artifacts:
| Signal | How to Check | What It Tells Us |
|---|---|---|
| Requirements docs | Glob("**/requirements*.md") |
Requirements exist |
| Use cases | Glob("**/use-case*.md") |
Use cases defined |
| User stories | Glob("**/user-stories*.md") |
Stories written |
| BPMN diagrams | Glob("**/*.bpmn") |
Process models exist |
| Stakeholder docs | Glob("**/stakeholder*.md") |
Stakeholders mapped |
.aidocs/ |
Glob("**/.aidocs/") |
SDD structure |
Read existing artifacts:
- Any requirements or spec documents
- constitution.md for business context
- Existing user stories or use cases
Discovery Questions
Q1: BA Activity Type
question: "What BA activity do you need help with?"
header: "Activity"
multiSelect: false
options:
- label: "Understand stakeholders"
description: "Map stakeholders, plan engagement"
- label: "Gather requirements"
description: "Elicitation, interviews, workshops"
- label: "Document requirements"
description: "Use cases, user stories, specs"
- label: "Model processes"
description: "BPMN, workflows, data models"
- label: "Analyze strategy"
description: "Current state, future state, gaps"
Routing:
- “Stakeholders” â
Skill(faion-ba-core)â stakeholder-analysis - “Gather” â
Skill(faion-ba-core)â elicitation-techniques - “Document” â
Skill(faion-ba-modeling)â use-cases, user-stories - “Model” â
Skill(faion-ba-modeling)â bpmn, data-models - “Strategy” â
Skill(faion-ba-core)â strategy-analysis
Q2: Requirements Format
question: "How should requirements be documented?"
header: "Format"
multiSelect: false
options:
- label: "User stories (Agile)"
description: "As a... I want... So that..."
- label: "Use cases (detailed)"
description: "Actor, preconditions, flow"
- label: "Functional requirements"
description: "System shall... statements"
- label: "Mixed / not sure"
description: "I'll recommend based on context"
Q3: Stakeholder Access
question: "Can you access stakeholders for elicitation?"
header: "Access"
multiSelect: false
options:
- label: "Yes, can interview/workshop"
description: "Direct stakeholder engagement"
- label: "Limited (email, async)"
description: "Remote, asynchronous"
- label: "No access (documents only)"
description: "Work from existing docs"
Context impact:
- “Direct” â Full elicitation techniques
- “Limited” â Surveys, document analysis
- “No access” â Document analysis, assumptions log
Architecture
faion-business-analyst (orchestrator)
âââ faion-business-analyst:core (21 methodologies)
â âââ Planning & Governance
â âââ Elicitation
â âââ Requirements Lifecycle
â âââ Strategy Analysis
â âââ Solution Evaluation
â âââ Modern Practices
âââ faion-business-analyst:modeling (7 methodologies)
âââ Behavioral Models (use cases, user stories)
âââ Process Models (BPMN)
âââ Data Models (ERD)
âââ Decision Models (business rules)
âââ Interface Models
âââ Validation Models (acceptance criteria)
Quick Decision
| If you need… | Sub-Skill | Key File |
|---|---|---|
| Define BA approach | ba-core | ba-planning.md |
| Map stakeholders | ba-core | stakeholder-analysis.md |
| Gather requirements | ba-core | elicitation-techniques.md |
| Track/prioritize requirements | ba-core | requirements-traceability.md, requirements-prioritization.md |
| Analyze strategy | ba-core | strategy-analysis.md |
| Evaluate solution | ba-core | solution-assessment.md |
| Model user interactions | ba-modeling | use-case-modeling.md, user-story-mapping.md |
| Map processes | ba-modeling | business-process-analysis.md |
| Model data | ba-modeling | data-analysis.md |
| Define business rules | ba-modeling | decision-analysis.md |
| Design interfaces | ba-modeling | interface-analysis.md |
| Write acceptance criteria | ba-modeling | acceptance-criteria.md |
6 Knowledge Areas
| # | Knowledge Area | Focus | Sub-Skill |
|---|---|---|---|
| 1 | BA Planning & Monitoring | Approach, stakeholders, governance | ba-core |
| 2 | Elicitation & Collaboration | Gather information | ba-core |
| 3 | Requirements Lifecycle | Trace, maintain, prioritize | ba-core |
| 4 | Strategy Analysis | Current/future state, gaps | ba-core |
| 5 | Requirements Analysis & Design | Model, verify, validate | ba-modeling |
| 6 | Solution Evaluation | Measure, assess, improve | ba-core |
Sub-Skills
faion-business-analyst:core (21 files)
Planning, elicitation, requirements lifecycle, strategy, evaluation, modern practices
Location: ~/.claude/skills/faion-business-analyst:core/
faion-business-analyst:modeling (7 files)
Use cases, user stories, BPMN, ERD, decision tables, interfaces, acceptance criteria
Location: ~/.claude/skills/faion-business-analyst:modeling/
Navigation
- Main orchestrator: This file
- Detailed overview: CLAUDE.md
- Knowledge Areas: knowledge-areas-detail.md
- References: ref-CLAUDE.md
BA Domain Skill v3.0 | 28 Methodologies | 2 Sub-Skills | 6 Knowledge Areas