メニュー
Business Analysis & Requirements Engineering. Use when: identifying stakeholders, eliciting or specifying requirements, prioritizing, validating, tracing, or managing requirements changes. Depends on fpf-core.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate compact, unambiguous FPF-structured output at F4-F5 formality level. Use when writing for AI agent consumers or FPF-literate humans where token economy and auditability matter: diagnostics, architecture decisions, code reviews, status reports, trust assessments, system compositions. Replaces verbose prose (F0) with typed-slot notation (~65% token savings, lossless). Do NOT use for: casual chat, teaching, non-technical audiences, creative tasks.
First Principles Framework core patterns. Use when doing engineering, research, management, or mixed human/AI work. ALWAYS use as governing patterns for any DPF or LPF work. Load individual patterns from references/ as needed — never read the full spec unless doing deep audit.
Spec-Decomposer: splits monolithic framework specifications (FPF/DPF/LPF) into atomic skill reference files. Use when: decomposing a framework monolith into skill references, updating references/ after monolith changes, or setting up a new DPF/LPF skill from a monolith. Depends on fpf-core, dpf-fpf-literacy, dpf-lfw-architecture.
FPF Literacy & DPF Authoring. Use when: helping an agent understand the FPF/DPF/LPF stack, creating a new DPF, loading domain knowledge into an agent, distinguishing FPF-grounded answers from generic AI responses, or choosing a carrier for publication. Depends on fpf-core.
LFW Architecture. Use when: organizing the FPF/DPF/LPF workspace, deciding where to place a new framework, setting up the skill-carrier structure, or resolving LPF vs Project boundary questions. Depends on fpf-core.
Guide for deciding when to create agent skills, how to design them well, and what anti-patterns to avoid. Use when: (1) creating a new skill, (2) deciding between skills vs AGENTS.md vs MCP vs Memory, (3) reviewing an existing skill for quality, (4) unsure if a skill is needed at all.
| name | dpf-business-analysis |
| description | Business Analysis & Requirements Engineering. Use when: identifying stakeholders, eliciting or specifying requirements, prioritizing, validating, tracing, or managing requirements changes. Depends on fpf-core. |
Depends on: fpf-core
Bounded context: Business Analysis in engineering projects
Source of truth: assets/BABusinessAnalysis-dpf.md
| Situation | Load | Governing cues → fpf-core |
|---|---|---|
| Stakeholder identification | references/stakeholder-identification.md | C.22.2, C.11 |
| Separating problem and solution | references/problem-vs-solution.md | A.16, C.22.2 |
| Requirements elicitation | references/requirement-elicitation.md | C.22.2, A.10 |
| Requirements specification | references/requirement-specification.md | E.8, A.19 |
| Requirements prioritization | references/requirement-prioritization.md | A.19, C.18 |
| Requirements validation | references/requirement-validation.md | A.10, B.3 |
| Requirements traceability | references/requirement-traceability.md | A.10, E.4.PFR |
| Requirements change management | references/requirement-change-management.md | E.23, G.2 |
| Business process modeling | references/business-process-modeling.md | E.17, C.30 |
| Use case modeling | references/use-case-modeling.md | E.17, E.8 |
| Data requirements | references/data-requirements.md | A.19, A.10 |
| Security requirements | references/security-requirements.md | B.3, A.20 |
references/. DO NOT read assets/BABusinessAnalysis-dpf.md.assets/BABusinessAnalysis-dpf.md. After edits — rebuild references/.Ready — 12 problem cards + INDEX + relations.