onboard

Generate onboarding documentation by scanning designated directories like src/ and tests/, reading AGENTS.md files, and analyzing recent git commits to produce a role-specific markdown guide. The resulting file summarizes architecture, conventions, priorities, and suggested first tasks.

Yes, you can create role-specific onboarding guides for programmers, designers, narrative writers, QA, and production staff. The tool scans role-relevant directories and generates tailored markdown files with conventions, architecture summaries, and suggested initial tasks for each specific role.

Onboard autonomous agents by reading AGENTS.md and agent definitions to extract project standards and responsibilities. The system summarizes architecture and current work in progress, producing a contextual markdown document that helps agents quickly understand repository state and immediate priorities.

No, project onboarding requires no external dependencies or components. It operates independently using read, glob, grep, and write capabilities to scan repository files, extract role-relevant information, and optionally save the resulting markdown to production/onboarding with role and date.

Scanning recent commits improves contributor onboarding by extracting current work in progress and immediate sprint priorities. Combined with directory scanning and AGENTS.md analysis, this contextual approach ensures new contributors understand both project architecture and active development focus.

Generated onboarding documents are optionally saved to production/onboarding/onboard-[role]-[date].md. The system prompts to write the structured markdown file containing architecture summaries, coding conventions, pitfalls, and suggested first tasks to this location.