メニュー
Business analysis: requirements engineering, stakeholder analysis, process modeling.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Architect Agent for the Apeiron workflow. Transforms structured requirements into document model designs — GraphQL state schemas, module/operation plans, subgraph type definitions, and editor component specs. Use when (1) requirements are ready and a schema needs designing, (2) a new document model needs modules and operations planned, (3) an existing model needs schema changes proposed, (4) subgraph types need to be designed for new fields, or (5) you need to plan how a feature maps to Powerhouse primitives. Triggers on: schema design, document model architecture, operation planning, module design, type design, subgraph planning, model proposal, specs.
Analyst Agent for the Apeiron workflow. Transforms raw business ideas, stakeholder input, and SME knowledge into structured requirements for Powerhouse document models. Use when (1) a new feature or document model is proposed but requirements are vague, (2) stakeholder needs must be captured and prioritized, (3) a PRD needs to be created or refined, (4) frontend data needs must be communicated to backend, or (5) starting any new workstream that will eventually become a document model. Triggers on: new feature request, requirements gathering, stakeholder analysis, PRD creation, business requirements, problem statement, feature proposal, demand signal.
Developer Agent for the Apeiron workflow. Implements document model changes — reducers, editors, subgraph resolvers — from an Architect's spec. Use when (1) a spec is ready and needs implementing, (2) reducers need to be written or updated, (3) editor components need to be built, (4) subgraph resolvers need mapping, (5) MCP actions need dispatching for schema changes, or (6) you're in the implementation phase of any document model workstream. Triggers on: implement spec, write reducer, build editor, implement operation, dispatch actions, code the schema, wire up subgraph, implement feature.
Reviewer Agent for the Apeiron workflow. Schema hygiene, document state verification, delivery checklist, and query field mapping for ALL Powerhouse document models in this repo. Use when (1) an implementation needs reviewing before merge, (2) checking a live document's state against its schema for unused/empty fields, (3) auditing a document model for dead weight, (4) verifying subgraph query types match the schema, (5) preparing a schema delivery for backend consumers, (6) running a weekly backend sync, or (7) running TypeScript/ESLint checks. Triggers on: schema audit, dead weight, field mapping, query fields, backend sync, delivery checklist, apeiron check, subgraph query, document state check, unused fields, review implementation, approve schema.
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
Build document models, editors, processors, subgraphs, and drive-apps for the Powerhouse/Vetra ecosystem. Use when Claude needs to (1) create or modify document models with GraphQL schemas and operations, (2) build React-based document editors with dispatch hooks, (3) work with Reactor-MCP tools for document and drive management, (4) implement pure synchronous reducers, (5) use the Powerhouse CLI (ph vetra, ph generate, ph connect), (6) design GraphQL state and input schemas with Powerhouse scalar types, (7) create subgraphs or processors, (8) deploy or publish Powerhouse packages, or any Powerhouse/Vetra development task. Triggers on mentions of: Powerhouse, Vetra, document model, reactor, MCP reactor, ph vetra, ph generate, switchboard, Connect Studio, drive, PHID, OID, document-engineering, reducer, dispatch, addActions.
| name | faion-business-analyst |
| description | Business analysis: requirements engineering, stakeholder analysis, process modeling. |
| user-invocable | false |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash(ls:*), Task, AskUserQuestion, TodoWrite |
Entry point:
/faion-net— invoke this skill for automatic routing to the appropriate domain.
Orchestrator for Business Analysis Framework (BABOK) practices
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:
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:
Skill(faion-ba-core) → stakeholder-analysisSkill(faion-ba-core) → elicitation-techniquesSkill(faion-ba-modeling) → use-cases, user-storiesSkill(faion-ba-modeling) → bpmn, data-modelsSkill(faion-ba-core) → strategy-analysisquestion: "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"
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:
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)
| 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 |
| # | 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 |
Planning, elicitation, requirements lifecycle, strategy, evaluation, modern practices
Location: ~/.claude/skills/faion-business-analyst:core/
Use cases, user stories, BPMN, ERD, decision tables, interfaces, acceptance criteria
Location: ~/.claude/skills/faion-business-analyst:modeling/
BA Domain Skill v3.0 | 28 Methodologies | 2 Sub-Skills | 6 Knowledge Areas