@majiayu000/comm-plan
Bコミュニケーションマネジメント計画書を作成する。情報共有計画、報告体制の策定時に使う。
Install
agr install @majiayu000/comm-plan --target claudeWrites 2 files into .claude/skills/, pinned to git-bcbcb305.
- .claude/skills/comm-plan/SKILL.md
- .claude/skills/comm-plan/metadata.json
Document
name: comm-plan description: コミュニケーションマネジメント計画書を作成する。情報共有計画、報告体制の策定時に使う。 phase: planning pmbok-area: communications
目的
ステークホルダーへの情報提供方法、頻度、責任者を明確化する。
トリガー語
- 「コミュニケーション計画を作成」
- 「報告体制を整理」
- 「情報共有計画を策定」
入力で最初に聞くこと
| # | 質問 | 必須 |
|---|---|---|
| 1 | プロジェクト名は? | ✓ |
| 2 | 主要ステークホルダーは? | - |
手順
Step 1: ステークホルダー分析
- 情報ニーズの特定
Step 2: コミュニケーションマトリクス作成
- 誰に/何を/いつ/どうやって
Step 3: 保存
workspace/{ProjectName}/docs/CommPlan.md
成果物
| 成果物 | 保存先 |
|---|---|
| コミュニケーション計画書 | workspace/{ProjectName}/docs/CommPlan.md |
検証(完了条件)
- ステークホルダーごとの情報ニーズが特定されている
- 報告頻度・手段が明記されている
参照
- Command:
.claude/commands/02_aipjm_02_planning_05_comm_plan.md
Repository README
Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.
Claude Skill Registry (Data)
This repo contains the archived skill contents (the heavy, browsable skill files).
Canonical layout
- Category folders at repo root (e.g.
development/,documents/,data/, ...) - Each skill lives under a category:
<category>/<skill>/SKILL.md+<category>/<skill>/metadata.json - Case conflicts are resolved with
{name}-{owner}-{repo}suffixes (fallback:-{short-hash}).
Archive status
- Live badges above are sourced from
claude-skill-registry-corestats.json. - Counts in this README are intentionally dynamic, not hardcoded.
- If the badges look stale, refresh the
corebuild/index pipeline rather than editing numbers here.
Where the index + site live
- Core repo: https://github.com/majiayu000/claude-skill-registry-core
- Main repo (merged publish artifact): https://github.com/majiayu000/claude-skill-registry
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-bcbcb3052d732026-07-31