knowledge-transfer-plan

Use when performing knowledge transfer plan — structures a knowledge transfer plan for engineering teams facing team transitions, departures, or domain ownership changes. This template ensures critical knowledge about systems, processes, and tribal context is documented, transferred to receiving team members, and validated before the transition is complete.

インストールへ移動

リポジトリ: cloudthinker-ai/CloudSkills
ソースの最終更新活動: 2026年3月23日 11:35
検出された SKILL.md の言語: 英語
スター: 7
フォーク: 3

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。

npx skills add https://github.com/cloudthinker-ai/CloudSkills --skill knowledge-transfer-plan

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md

ソースの指示 · 読み取り専用プレビュー

検索に戻るインストールに戻る

analytics-cloudflare

Cloudflare GraphQL Analytics for zone traffic, firewall events, Workers metrics, and schema exploration. Use when querying Cloudflare analytics data or exploring the GraphQL API.

2026-04-05

analyzing-postgres

PostgreSQL database analysis, performance tuning, and health monitoring. You MUST read this entire skill document before executing any PostgreSQL operations — it contains mandatory workflows, safety constraints, and two-phase execution rules that prevent common errors like hallucinated column names and unsafe queries.

2026-04-05

analyzing-sonarqube

SonarQube code quality and security analysis. Use when working with code quality metrics, security hotspots, quality gates, or issue tracking in SonarQube Cloud or Server.

2026-04-05

このリポジトリのすべてを見る

name	knowledge-transfer-plan
enabled	true
description	Use when performing knowledge transfer plan — structures a knowledge transfer plan for engineering teams facing team transitions, departures, or domain ownership changes. This template ensures critical knowledge about systems, processes, and tribal context is documented, transferred to receiving team members, and validated before the transition is complete.
required_connections	[{"prefix":"collaboration","label":"Collaboration Tool"},{"prefix":"ticketing","label":"Ticketing System"}]
config_fields	[{"key":"transfer_reason","label":"Transfer Reason","required":true,"placeholder":"e.g., Team member departure, ownership transfer, re-org"},{"key":"source_person","label":"Knowledge Source (Person/Team)","required":true,"placeholder":"e.g., Jane Smith or Platform Team"},{"key":"target_person","label":"Knowledge Recipient (Person/Team)","required":true,"placeholder":"e.g., John Doe or API Team"},{"key":"deadline","label":"Transfer Deadline","required":true,"placeholder":"e.g., 2026-04-15"}]
features	["KNOWLEDGE_TRANSFER","ENGINEERING_MANAGEMENT","DOCUMENTATION"]

name	knowledge-transfer-plan
enabled	true
description	Use when performing knowledge transfer plan — structures a knowledge transfer plan for engineering teams facing team transitions, departures, or domain ownership changes. This template ensures critical knowledge about systems, processes, and tribal context is documented, transferred to receiving team members, and validated before the transition is complete.
required_connections	[{"prefix":"collaboration","label":"Collaboration Tool"},{"prefix":"ticketing","label":"Ticketing System"}]
config_fields	[{"key":"transfer_reason","label":"Transfer Reason","required":true,"placeholder":"e.g., Team member departure, ownership transfer, re-org"},{"key":"source_person","label":"Knowledge Source (Person/Team)","required":true,"placeholder":"e.g., Jane Smith or Platform Team"},{"key":"target_person","label":"Knowledge Recipient (Person/Team)","required":true,"placeholder":"e.g., John Doe or API Team"},{"key":"deadline","label":"Transfer Deadline","required":true,"placeholder":"e.g., 2026-04-15"}]
features	["KNOWLEDGE_TRANSFER","ENGINEERING_MANAGEMENT","DOCUMENTATION"]

Validation Task	Status	Notes
Recipient can deploy the service independently
Recipient can diagnose and resolve common issues
Recipient can handle an on-call page for the service
Recipient knows who to escalate to for edge cases
All critical documentation is reviewed and accurate
Access and credentials are transferred

Shortcut	Counter	Why
"We can skip some steps for this case"	Adapt the workflow steps, don't skip them	Skipped steps are where incidents and oversights originate
"The user seems to already know what to do"	Complete all workflow phases with the user	The workflow catches blind spots that experience alone misses
"This is a minor case, full process is overkill"	Scale the process down, don't turn it off	Minor cases become major when unstructured; the process scales, not disappears
"I'll fill in the details later"	Complete each section before moving on	Deferred details are forgotten; real-time capture is more accurate
"The template output isn't necessary"	Always produce the structured output format	Structured output enables comparison, audit trails, and handoff to other teams

knowledge-transfer-plan

インストール方法

ソースファイルを確認