onboarding-checklist

To generate a role-based onboarding checklist, provide the new team member's name and seniority profile (Júnior, Pleno, Sênior, or Tech Lead). The system filters documented engineering processes and contexts to output a personalized checklist.

Yes, you can create onboarding checklists for different seniority levels. The system filters checklist items based on defined profiles such as Júnior, Pleno, Sênior, and Tech Lead to match the developer's specific role requirements.

Context validation checks that all referenced onboarding context files exist by performing filesystem reads. It omits missing items from the generated checklist and alerts you at the end if any documented contexts are missing.

Generating an onboarding checklist will not modify your repository. It provides chat-only, safe guidance without editing code, creating pull requests, issues, or accessing sensitive configuration files.

You need to provide the new team member's name and profile to start generation. The system uses these inputs to validate referenced context files and produce a role-aware onboarding checklist for the developer.

If an onboarding context file is missing from your repository, the system omits the missing items from the checklist and alerts you at the end. This ensures the generated checklist only includes validated, existing documentation contexts.