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.

Ir para a instalação

Repositório: cloudthinker-ai/CloudSkills
Última atividade na origem: 23 de março de 2026 às 11:35
Idioma detectado do SKILL.md: inglês
Estrelas: 7
Forks: 3

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

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

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

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

Opções de instalação

Revise os arquivos de origem