create-onboarding-guide

To generate a developer onboarding guide, the Skill scans your repository's .chalk/docs/ directories and codebase to synthesize a structured Day 1 / Week 1 / Month 1 reading path. It outputs a comprehensive markdown file with runnable steps and required references.

The best way to structure a developer ramp-up plan is using a Day 1 / Week 1 / Month 1 progression. This covers environment setup, first commit, architecture overview, and ownership, ensuring new developers progress logically through their onboarding journey.

You can identify documentation gaps by analyzing the repository codebase and existing docs to find missing information. The Skill lists these missing docs as actionable TODOs within the generated onboarding guide for future knowledge transfer work.

Yes, you can automate runbook creation by pulling content from existing .chalk/docs/ directories and the codebase. The Skill synthesizes these sources to produce an ordered reading list, marking required versus reference documentation automatically.

Yes, the onboarding guide generation works without external dependencies. The Skill operates independently to scan repository docs and code, requiring only your existing codebase and .chalk/docs/ directories to build the complete learning path.

The Day 1 section includes environment setup and the first commit. It is part of a structured progression that pulls runnable steps and required documentation from your codebase to get developers contributing immediately.