メニュー
Business Analysis & Requirements Engineering. Use when: identifying stakeholders, eliciting or specifying requirements, prioritizing, validating, tracing, or managing requirements changes. Depends on fpf-core.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/dimonier/skills --skill dpf-business-analysisコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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.
Maintains project state in a markdown vault (key decisions, open questions, risks, contradictions, dependencies) from meeting transcripts, structured notes, PDF documents, or owner chat updates. Governs working tracks as the mandatory container for all productive activity (research, analysis, synthesis). Use for updating project-vault after meetings, dialog briefings, decision records, and next-meeting agendas. Triggers: project state, transcripts, meeting notes, PDF documents, chat updates, risks, dependencies, contradictions, ADR-style decisions, track creation and lifecycle, inbox processing.
Sync the fpf-core skill from the canonical FPF-Spec.md monolith. Use when: (1) the FPF specification has been updated (git pull shows new commits), (2) the fpf-core skill references/ are stale or show wrong counts, (3) running scheduled maintenance on LFW skills. Self-contained — bundles decompose_fpf.py + _common.py directly. No dependencies on external skills. Works only with the local skill at `../fpf-core/` (relative to this skill) — NOT the global user skill.
| 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.