writing-onboarding-guide

What problem does it solve?

This Skill helps you write onboarding documents for launches that must serve multiple reader profiles without collapsing into a single generic voice. It prevents the common failure mode where engineers need implementation detail, executives need decision context, and scientists need validation detail, but one document tries to satisfy everyone and ends up serving nobody well.

Core Features & Use Cases

• Audience-specific sections: Separates the document into clear sections for engineers, scientists, executives, auditors, learners, or instructors, each with the right depth ceiling.
• Shared front matter: Produces a TL;DR with owner, channel, status, and explicit out-of-scope boundaries so every reader can orient quickly.
• Documentation guardrails: Enforces audience openers, a shared glossary, cross-audience navigation, and a single feedback channel to keep the document coherent.
• Use cases: Launching a new internal service, onboarding a dataset or model, fixing a README that gets conflicting feedback, or replacing a single-voice doc that is being asked to do too many jobs.

Quick Start

Ask Claude to draft a multi-audience onboarding guide for your system with separate reader sections, a front-loaded TL;DR, a shared glossary, and an explicit out-of-scope statement.