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

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 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

查看这个仓库的全部 Skills

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

安装方式

检查来源文件