Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

faion-business-analyst

Étoiles0

Forks0

Mis à jour10 février 2026 à 18:16

Business analysis: requirements engineering, stakeholder analysis, process modeling.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

powerhouse-inc

powerhouse-inc/service-offering

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en gestionProfessions des affaires et des opérations financières·SOC 13-1111

Explorateur de fichiers

100 fichiers

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

apeiron-architect

powerhouse-inc/service-offering

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.

2026-03-030

apeiron-business-analyst

powerhouse-inc/service-offering

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.

2026-03-030

apeiron-developer

powerhouse-inc/service-offering

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.

2026-03-030

apeiron-reviewer

powerhouse-inc/service-offering

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.

2026-03-030

ui-ux-pro-max

powerhouse-inc/service-offering

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.

2026-02-190

powervetra

powerhouse-inc/service-offering

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.

2026-02-130

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.

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