This skill should be used when creating comprehensive project plans for system development or implementation projects. Use this skill when you need to create Project Charters, Project Plans, WBS, Gantt Charts, RACI matrices, Risk analysis, or other PMBOK-aligned project management artifacts. Outputs are in Markdown format with Mermaid diagrams for visualizations. Leverages comprehensive PM knowledge base in references/ directory (544KB, 11 files) including PMBOK standards, Software/SaaS best practices, IT industry guidance, and specialized PM methodologies.
Instalación
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
This skill should be used when creating comprehensive project plans for system development or implementation projects. Use this skill when you need to create Project Charters, Project Plans, WBS, Gantt Charts, RACI matrices, Risk analysis, or other PMBOK-aligned project management artifacts. Outputs are in Markdown format with Mermaid diagrams for visualizations. Leverages comprehensive PM knowledge base in references/ directory (544KB, 11 files) including PMBOK standards, Software/SaaS best practices, IT industry guidance, and specialized PM methodologies.
Project Plan Creator（プロジェクト計画作成）
Overview
This skill transforms project requirements and stakeholder needs into comprehensive, PMBOK-aligned project management artifacts. It guides you through charter creation, scope definition, WBS development, scheduling with Gantt charts, resource planning with RACI matrices, and risk management planning.
Primary language: Japanese (default) with English support
Output format: Markdown + Mermaid diagrams
Framework alignment: PMBOK® Guide (6th, 7th, 8th editions)
Use this skill when:
Starting a new system development or implementation project
You need to create a Project Charter to formally authorize the project
You need to develop a comprehensive Project Plan with WBS, schedule, and resource allocation
You want to visualize project structure with Mermaid diagrams (Gantt, WBS, workflows)
You need PMBOK-compliant project documentation
You want to leverage PMBOK standards, DevOps/Agile best practices, and IT PM guidance from the references/ knowledge base
Core Workflows
Project Charter Creation: Create PMBOK-compliant project charters to formally authorize projects
Scope Definition and Management: Define project scope with clear boundaries and WBS
Schedule Development: Create detailed schedules with Mermaid Gantt charts
Resource Planning and RACI Matrix: Define team structure and assign responsibilities
Risk Management Planning: Identify, analyze, and plan responses for project risks
Communication and Quality Planning: Establish communication protocols and quality standards
Integration and Document Generation: Integrate all planning artifacts into cohesive project plan
Workflow 1: Project Charter Creation
Purpose
Create a formal document that authorizes the project, names the project manager, and gives authority to apply resources to project activities. The charter establishes the partnership between the performing organization and requesting organization.
Step 1: Gather Charter Inputs
Collect information from stakeholders:
Business Case: Why is this project needed? What problem does it solve?
graph TB
A[プロジェクトスコープ] --> B[In Scope]
A --> C[Out of Scope]
B --> B1[システム開発<br/>顧客・受注・在庫管理]
B --> B2[データ移行<br/>既存DBから新DB]
B --> B3[トレーニング<br/>3回実施]
B --> B4[ドキュメント<br/>設計書・マニュアル]
C --> C1[既存システム保守<br/>並行稼働中のサポート]
C --> C2[ハードウェア調達<br/>IT部が別途対応]
C --> C3[組織変更<br/>業務部門が実施]
C --> C4[カスタマイズ<br/>稼働後の追加開発]
Step 3: Develop Work Breakdown Structure (WBS)
Create hierarchical decomposition of project work. Use assets/project_plan_template.md Section 4 as reference.
WBS Example with Mermaid:
graph TD
A[ECサイト構築プロジェクト] --> B[1. 要件定義]
A --> C[2. 設計]
A --> D[3. 実装]
A --> E[4. テスト]
A --> F[5. デプロイ]
A --> G[6. PM]
B --> B1[1.1 現状分析]
B --> B2[1.2 機能要件定義]
B --> B3[1.3 非機能要件定義]
B --> B4[1.4 要件レビュー]
C --> C1[2.1 基本設計]
C --> C2[2.2 詳細設計]
C --> C3[2.3 DB設計]
C --> C4[2.4 設計レビュー]
D --> D1[3.1 フロントエンド開発]
D --> D2[3.2 バックエンド開発]
D --> D3[3.3 DB構築]
D --> D4[3.4 統合]
Document the approved scope baseline consisting of:
Project Scope Statement: Detailed description of project and product scope
WBS: Visual and tabular representation
WBS Dictionary: Detailed descriptions of WBS components
Step 5: Define Scope Change Control Process
変更管理プロセス:
graph TD
A[変更要求提出] --> B[変更要求記録]
B --> C{軽微な変更?}
C -->|Yes<br/>工数5人日以下| D[PM承認]
C -->|No<br/>工数5人日超| E[影響分析実施]
E --> F[スコープ・スケジュール・コストへの影響評価]
F --> G[CCB審議]
G --> H{承認?}
H -->|Yes| I[スコープベースライン更新]
H -->|No| J[却下/保留]
I --> K[変更実施]
D --> K
J --> L[要求者へ通知]
K --> L
Workflow 3: Schedule Development with Gantt Charts
Purpose
Create a detailed project schedule with task dependencies, resource assignments, and critical path visualization using Mermaid Gantt charts.
Step 1: Define Activities
For each WBS work package, define specific activities:
Use assets/project_plan_template.md Section 7 structure:
RACI Matrix:
| タスク/成果物 | Sponsor | PO | PM | Tech Lead | BA | SE | QA |
|-------------|---------|----|----|-----------|----|----|-----|
| プロジェクト計画 | A | C | R | C | C | I | I |
| 要件定義 | I | A | C | C | R | I | I |
| 基本設計 | I | C | A | R | C | I | I |
| 詳細設計 | I | I | A | R | I | C | C |
| 実装 | I | I | A | R | I | R | I |
| 単体テスト | I | I | A | C | I | R | C |
| 統合テスト | I | C | A | C | I | C | R |
| 受け入れテスト | I | A | R | I | C | I | R |
| 本番リリース | A | C | R | R | I | C | C |
凡例:
R (Responsible) = 実行責任者
A (Accountable) = 説明責任者（最終意思決定者）
C (Consulted) = 相談先（事前に意見を聞く）
I (Informed) = 報告先（結果を報告）
Use assets/project_plan_template.md Section 8 Mermaid diagram:
graph LR
A[リスク識別] --> B[リスク分析]
B --> C[リスク対応計画]
C --> D[リスク監視]
D --> E{リスク発生?}
E -->|Yes| F[対応措置実施]
E -->|No| D
F --> G[効果測定]
G --> D
D --> H{新リスク?}
H -->|Yes| A
H -->|No| D
リスクレビュー頻度:
高リスク: 毎週レビュー
中リスク: 隔週レビュー
低リスク: 月次レビュー
Workflow 6: Communication and Quality Planning
Purpose
Establish communication protocols, reporting structures, and quality assurance processes to ensure stakeholder alignment and deliverable quality.
graph LR
A[設計] --> B[設計レビュー]
B --> C{承認?}
C -->|No| A
C -->|Yes| D[実装]
D --> E[コードレビュー]
E --> F{承認?}
F -->|No| D
F -->|Yes| G[単体テスト]
G --> H[静的解析]
H --> I{品質基準達成?}
I -->|No| D
I -->|Yes| J[統合テスト]
