onboard

Generates a role-specific onboarding document from project state, architecture, and conventions.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill onboard-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/dnkrow/skill/tree/main/claude-global/onboard
Command: npx skills add https://github.com/dnkrow/skill --skill onboard-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork for new contributors by generating a clear, role-specific onboarding document that summarizes the project’s current state, architecture, conventions, and priorities.

Core Features & Use Cases

  • Project context loading: Reads the main CLAUDE.md overview and (optionally) a matching role definition from .claude/agents to align the onboarding with how the project expects work to be done.
  • Targeted area scanning: Scans the most relevant directories for the specified role/area (e.g., src/, design/, design/narrative/, tests/, production/) and incorporates recent change signals when available.
  • Actionable onboarding output: Produces a structured document with key directories/files, standards, current state, sprint context, dependencies, pitfalls, first tasks, and questions to ask.

Quick Start

Run the onboard skill with an argument like "onboard developer" to generate an onboarding document tailored to that role.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I generate a role-based onboarding document for a new contributor?

Generate a role-based onboarding document by scanning relevant project directories and summarizing architecture, conventions, and sprint priorities into a structured markdown file. The output aligns new contributors with project state and role-specific expectations quickly.

What is the best way to onboard a new developer to project conventions and architecture?

Onboarding a new developer to project conventions requires summarizing the project state, architecture, and current priorities. A generated onboarding brief reads project overviews and scans directories to produce actionable role-specific orientation documentation.

Can I create onboarding briefs for non-programming roles like design or QA?

Yes, you can create onboarding briefs for design, narrative, QA, and production workflows. The generation process scans role-relevant directories and produces orientation documentation tailored to the specific needs of those non-programming areas.

How do I use CLAUDE.md and agent definitions to set up project context for onboarding?

Use CLAUDE.md to provide the main project overview and .claude/agents for role definitions. The onboarding generation reads these files to align the output document with how the project expects work to be done for a specific role.

Does generating an onboarding brief require any external dependencies or modules?

Generating an onboarding brief requires no external dependencies or modules. It operates standalone by reading project files like CLAUDE.md, scanning local directories, and outputting a markdown file upon user approval.

What information is included in a generated contributor onboarding summary?

A generated contributor onboarding summary includes key directories, files, standards, current state, sprint context, dependencies, pitfalls, first tasks, and questions to ask. This ensures new team members understand both architecture and immediate priorities.