onboard

Role-specific onboarding documentation is generated by reading project concepts, conventions, architecture references, and sprint plans to tailor content for a specific role, outputting a single markdown file with relevant first tasks.

Automating contributor onboarding involves processing project context like design concepts and session state to produce a tailored document for roles such as engineer, designer, PM, or QA, ensuring consistent guidance without manual writing.

Creating onboarding docs that adapt to sprint plans requires reading active session state and sprint context files to tailor the generated documentation to the project's current development phase and immediate tasks.

Generating tailored onboarding documentation relies on project context files like concept.md, technical-preferences.md, systems-index.md, and active.md; if these key sources are missing, the process surfaces blockers instead of guessing.

When key project context is missing during onboarding document generation, the process surfaces specific blockers rather than producing incomplete guidance, ensuring contributors are aware of missing architecture or sprint references.

Automated onboarding document generation supports both technical and non-technical roles by reading the same project context and tailoring the output document to fit engineers, designers, PMs, and QA contributors appropriately.