Team onboarding

Overview

/team-onboarding generates a customized onboarding.md in the project root based on your team's Friday usage from the last 30 days. It analyzes top skills, MCP servers, and codebases, then asks a few questions to personalize the guide for your team. The result is a ready-to-share onboarding document for new team members.

Quick Start

/team-onboarding

No arguments needed. Friday analyzes your usage, generates a draft, then asks 3 questions to personalize it.

Usage

What gets analyzed

Friday looks at the last 30 days of usage to identify your top skills (with a visual usage distribution), top MCP servers, and codebases worked on. Sections are omitted from the output if there is no data for them.

Personalization

After generating the draft, an agent asks for three things: your team name, any team tips you want to include, and get started content for new members. These replace placeholder sections in the generated guide.

Output

The command creates onboarding.md in the project root. The file is ready to share with new team members as-is or with further edits.

Command palette

/team-onboarding is also accessible via the command palette by searching "team-onboarding".

Examples

Basic invocation:

/team-onboarding

After generating the draft, the agent asks three personalization questions: what to name the team section, what team tips to include, and what get started content to add for new members.

The resulting onboarding.md contains the following sections: a team name header, a "How we use Friday" section with skill and MCP usage charts, a setup checklist covering codebases, MCP servers, and skills, a team tips section, and a get started section.