knowledge-transfer

Generates knowledge transfer checklists and handover documentation for project closure.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill knowledge-transfer-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-transfer
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/closure/knowledge-transfer
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill knowledge-transfer-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project handovers often fail because critical operational knowledge stays with the departing team. This Skill produces a structured, sign-off-gated knowledge transfer document so operations and support teams can take over a system with documented training, access, and escalation paths. ## Core Features & Use Cases - Handover Checklists: Generates system, operational, support, and business knowledge checklists with provider, receiver, and completion status tracking. - Training and Access Plans: Produces a training session schedule, hands-on exercises, and access/credential transfer tables. - Governance Integration: Enforces validation rules, a signed closure-report prerequisite, sources file generation, and Project Manager approval as the final skill of Phase 13 (Closure). - Use Case: At the end of a software project, generate a knowledge transfer document that schedules training sessions, inventories all documentation, and captures sign-off from operations and support leads before the project team disengages. ## Quick Start Ask the agent to run the knowledge-transfer skill to create the Phase 13 closure handover document for your project.

Frequently Asked Questions about knowledge-transfer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a knowledge transfer document for project handover?▼

Invoke the knowledge-transfer skill after the closure-report is signed. It gathers project name, receiving team, timeline, and critical systems, then generates a Markdown document with checklists, training plans, and sign-off tables at documentation/13-closure/knowledge-transfer.md.

What should a knowledge transfer checklist include?▼

A knowledge transfer checklist should cover system architecture, operational procedures like deployment and monitoring, support knowledge such as troubleshooting and escalation, and business context like stakeholders and SLAs. This skill generates all four categories with provider, receiver, and status tracking.

What prerequisites are required before running this skill?▼

The closure-report document must exist and be signed before this skill runs. It also consumes inputs from technical documentation, operations runbooks, and architecture design documents produced by earlier skills in the SDLC pipeline.

Who approves the knowledge transfer document?▼

The Project Manager holds final approval authority for the knowledge transfer document. Operations Lead and Technical Lead provide content reviews, but their reviews do not gate the signature.

Why does the knowledge transfer skill block signature requests?▼

Signatures are blocked when validation rules fail, such as unsigned prerequisites, placeholder text, empty sections, malformed document IDs, or broken cross-references. The agent must fix these issues through the improvement flow before requesting sign-off.