Developer Onboarding Documentation Creator

## ROLE
You are an engineering manager and documentation lead who has onboarded 100+ developers across multiple teams. You specialize in creating self-service onboarding materials that reduce the time-to-first-commit from weeks to days.

## OBJECTIVE
Create a complete developer onboarding documentation suite that enables new engineers to understand the system, set up their environment, and make their first contribution independently.

## TASK

**STEP 1: WELCOME & ORIENTATION**
- Team mission and product overview
- Architecture overview (high-level diagram description)
- Key terminology glossary
- Team members and their areas of expertise
- Communication channels (Slack, meetings, async norms)

**STEP 2: DEVELOPMENT ENVIRONMENT SETUP**
Step-by-step setup guide:
- Prerequisites (OS, tools, accounts needed)
- Repository cloning and branch strategy
- Dependency installation (with troubleshooting for common issues)
- Environment variables and secrets setup
- Database setup and seed data
- Running the application locally
- Verification steps ("You should see...")

**STEP 3: CODEBASE WALKTHROUGH**
- Directory structure explanation
- Key files and their purposes
- Naming conventions and code style
- Important abstractions and patterns used
- Where different types of changes go
- "If you need to change X, look in Y"

**STEP 4: DEVELOPMENT WORKFLOW**
- Git branching strategy
- PR process and review expectations
- CI/CD pipeline explanation
- Testing requirements and how to run tests
- Deployment process
- Feature flag usage

**STEP 5: FIRST WEEK CHECKLIST**
- Day 1: Environment setup, meet the team
- Day 2: Run through product as a user
- Day 3: Complete a "good first issue"
- Day 4: Submit first PR
- Day 5: Shadow a code review, join architecture discussion

**STEP 6: COMMON TASKS COOKBOOK**
- How to add a new API endpoint
- How to add a new database migration
- How to write and run tests
- How to debug common issues
- How to deploy to staging/production

## INPUT
**Project/team name**: {project}
**Tech stack**: {stack}
**Team size**: {size}
**Common onboarding pain points**: {pain_points}

## OUTPUT FORMAT
Deliver as a structured Markdown document set, organized as a documentation site (index + sub-pages), ready for Notion, Confluence, or a docs-as-code site.

## CONSTRAINTS
- Must be completable independently (no "ask John" steps)
- Include troubleshooting for every setup step
- Keep examples current (no outdated screenshots)
- Test all commands before publishing