skills.rest
gleanwork
gleanworkOFFICIAL
Explore all skills by this author →
Website𝕏@gleanGitHub

project-handoff

Generate handoff documents with project context, people, and open items via Glean MCP tools.

25|8|Updated Dec 8, 2025
Search Tags:#knowledge transfer#document generation#team collaboration#transition#project handoff
One-click install
npx skills add https://github.com/gleanwork/claude-plugins --skill project-handoff-gleanwork
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-handoff
Source: https://github.com/gleanwork/claude-plugins/tree/main/plugins/glean/skills/project-handoff
Command: npx skills add https://github.com/gleanwork/claude-plugins --skill project-handoff-gleanwork

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of generating comprehensive handoff documents for new project owners, ensuring a smooth transition of knowledge and responsibilities.

Core Features & Use Cases

  • Detailed Handoff: Automatically creates a comprehensive handoff document covering current state, key people, tribal knowledge, open items, and a first-30-days plan.
  • Contextual Awareness: Identifies the project from user input and gathers relevant documentation, people, and decisions.
  • Customization: Allows for the inclusion of tribal knowledge, risks, and critical relationships specific to the project.
  • Use Case: Ideal for users who need to document a project before going on PTO, leaving, or changing teams.

Quick Start

Generate a handoff document for project 'XYZ'.

Frequently Asked Questions about project-handoff

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

FAQPage Schema
How do I create a project handoff document for a new owner?▼

Generating a handoff document involves synthesizing project information, tribal knowledge, and open items using standard Glean MCP tools. It automatically targets project context, people, and knowledge transfer for new owners.

What should a comprehensive project transition plan include?▼

A detailed handoff document covers the current project state, key people, tribal knowledge, open items, and a first-30-days plan, ensuring a smooth transition of knowledge and responsibilities.

Can I document tribal knowledge and risks before changing teams?▼

Yes, the process allows for the inclusion of tribal knowledge, risks, and critical relationships specific to the project. This ensures undocumented knowledge is captured before you leave or change teams.

Does generating handoff documents require a Glean MCP server connection?▼

Yes, generating handoff documents requires a Glean MCP server connection for tool access and data retrieval. It uses standard Glean MCP tools to gather relevant documentation, people, and decisions.

When do I need to generate a knowledge transfer document?▼

You need to generate a knowledge transfer document when preparing for a project transition, such as before going on PTO, leaving the company, or changing teams. This ensures new owners have a detailed first-30-days plan.

Related Skills

Explore More Product & Management Skills→
gleanworkgleanwork
25

connect-glean

Connect to a Glean MCP server using OAuth authentication.

Official
Intermediate
tomaszstaniaktomaszstaniak

first-90-days

Diagnose STARS situations and sequence a 30-60-90 leadership transition plan.

Community
Intermediate
zircotezircote
20

mnemonic-agent-coordination

Coordinate agents in-session with swarm tools and cross-session via blackboard files.

Community
Intermediate
arjunrattan-lab-aiarjunrattan-lab-ai

atpm-pdp

Generate and review Motive Product Development Plans from project management research artifacts.

Community
Advanced