[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C282FH9DSA5CN23EMJCSDM":3,"skill-same:01M6C282FH9DSA5CN23EMJCSDM":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":84},"01M6C282FH9DSA5CN23EMJCSDM","flow-team-onboarding",null,"Orchestrate Team Onboarding flow with pre-boarding, training, buddy assignment, and 30\u002F60\u002F90 day check-ins","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Fflow-team-onboarding\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"flow","flow team onboarding","onboarding","team","with","task","standard","true","sonnet","buddy","check","interactive","coding","start","write","read","text","orchestration","training","orchestrate","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: flow-team-onboarding\nplatforms: [all]\ndescription: Orchestrate Team Onboarding flow with pre-boarding, training, buddy assignment, and 30\u002F60\u002F90 day check-ins\ncommandHint:\n  argumentHint: \u003Cteam-member-name> [role] [start-date] [--guidance \"text\"] [--interactive]\n  allowedTools: Task, Read, Write, Glob, TodoWrite\n  model: sonnet\n  category: sdlc-orchestration\n  orchestration: true\n  modelRole: coding\n  modelTier: standard\n---\n\n> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-team-onboarding.playbook.yaml` (source of truth for the step\n> sequence + gates). This SKILL.md remains the discoverable trigger surface and prose\n> reference. See epic #1534.\n\n# Team Onboarding Flow\n\n**You are the Core Orchestrator** for team member onboarding, ensuring systematic integration with proper knowledge transfer and milestone-based progression.\n\n## Your Role\n\n**You orchestrate multi-agent workflows. You do NOT execute bash scripts.**\n\nWhen the user requests this flow (via natural language or explicit command):\n\n1. **Interpret the request** and confirm understanding\n2. **Read this template** as your orchestration guide\n3. **Extract agent assignments** and workflow steps\n4. **Delegate agents with the current provider-native orchestration mechanism** in the correct sequence\n5. **Synthesize results** and track progress\n6. **Report completion** with onboarding status\n\n## Onboarding Process Overview\n\n**Purpose**: Systematically integrate new team members with structured ramp-up, knowledge transfer, and milestone-based validation\n\n**Duration**: 90 days (30\u002F60\u002F90 day milestones)\n\n**Success Criteria**:\n- Pre-boarding checklist 100% complete by start date\n- Buddy assigned with pairing cadence established\n- 30\u002F60\u002F90 day milestones achieved on schedule\n- Full productivity reached by day 90\n- Onboarding feedback collected for process improvement\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Onboard [name] as [role]\"\n- \"Add team member [name]\"\n- \"New team member [name] starting [date]\"\n- \"Onboard new developer\"\n- \"Add [name] to the team\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Parameter Handling\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor onboarding focus\n\n**Examples**:\n```\n--guidance \"Technical architect role, focus on security and infrastructure\"\n--guidance \"Junior developer, needs extra mentorship and pairing\"\n--guidance \"Remote team member in different timezone, coordinate async\"\n--guidance \"Fast-track onboarding for urgent project needs\"\n```\n\n**How to Apply**:\n- Parse guidance for role specifics (seniority, domain focus)\n- Adjust buddy assignment (match expertise areas)\n- Modify training intensity (junior vs senior needs)\n- Adapt communication approach (remote vs local)\n\n### --interactive Parameter\n\n**Purpose**: You ask 6 strategic questions to understand onboarding needs\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 6 strategic questions to tailor this onboarding flow:\n\nQ1: What are your top priorities for this new team member?\n    (e.g., specific skills, project ownership, team collaboration)\n\nQ2: What are your biggest constraints for onboarding?\n    (e.g., timeline, buddy availability, remote coordination)\n\nQ3: What risks concern you most for this onboarding?\n    (e.g., skill gaps, team fit, ramp-up speed)\n\nQ4: What's your team's experience level with onboarding?\n    (helps calibrate support level and documentation needs)\n\nQ5: What's your target timeline for full productivity?\n    (typical: 90 days, urgent: 30-60 days)\n\nQ6: Are there compliance or security clearance requirements?\n    (e.g., background checks, training certifications)\n\nBased on your answers, I'll adjust:\n- Buddy selection and pairing intensity\n- Training schedule and focus areas\n- Milestone targets and check-in frequency\n- Documentation and access requirements\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance for execution\n\n## Artifacts to Generate\n\n**Primary Deliverables**:\n- **Pre-Boarding Checklist**: System access, equipment, documentation → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fpre-boarding-checklist.md`\n- **Onboarding Plan**: Personalized 90-day plan → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fonboarding-plan.md`\n- **Buddy Assignment**: Buddy responsibilities and schedule → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fbuddy-assignment.md`\n- **Starter Tasks**: Sequenced tasks with acceptance criteria → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fstarter-tasks.md`\n- **30-Day Check-In Report**: Milestone review → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F30-day-checkin.md`\n- **60-Day Check-In Report**: Performance assessment → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F60-day-checkin.md`\n- **90-Day Check-In Report**: Full integration validation → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F90-day-checkin.md`\n- **Onboarding Status Report**: Current progress tracker → `.aiwg\u002Freports\u002Fonboarding-status-{name}.md`\n\n**Supporting Artifacts**:\n- Training schedule and materials\n- Knowledge transfer documentation\n- Feedback collection forms\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Pre-Boarding Preparation\n\n**Purpose**: Ensure all systems, equipment, and documentation ready before start date\n\n**Your Actions**:\n\n1. **Initialize Onboarding Workspace**:\n   ```\n   Create directory structure:\n   .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F\n   ├── pre-boarding\u002F\n   ├── training\u002F\n   ├── check-ins\u002F\n   └── feedback\u002F\n   ```\n\n2. **Launch Pre-Boarding Agents** (parallel):\n   ```\n   # Agent 1: HR Coordinator\n   Task(\n       subagent_type=\"human-resources-coordinator\",\n       description=\"Prepare pre-boarding checklist and paperwork\",\n       prompt=\"\"\"\n       Create pre-boarding checklist for new team member:\n       - Name: {name}\n       - Role: {role}\n       - Start Date: {start-date}\n\n       Document requirements:\n       1. System Access\n          - [ ] Git repository access (read\u002Fwrite)\n          - [ ] CI\u002FCD pipeline access\n          - [ ] Issue tracker account\n          - [ ] Monitoring\u002Flogging tools\n          - [ ] Communication channels (Slack, email lists)\n          - [ ] VPN credentials\n          - [ ] SSO\u002FMFA setup\n\n       2. Equipment\n          - [ ] Laptop provisioned with OS and dev tools\n          - [ ] Monitor(s) and peripherals\n          - [ ] Security badge\u002Faccess card\n\n       3. Documentation\n          - [ ] Project README and CLAUDE.md\n          - [ ] Architecture documentation\n          - [ ] Runbooks and procedures\n          - [ ] Team conventions\n\n       4. First Day Logistics\n          - [ ] Welcome email with agenda\n          - [ ] Meeting invites sent\n          - [ ] Workspace prepared\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fpre-boarding-checklist.md\n       \"\"\"\n   )\n\n   # Agent 2: Operations Liaison\n   Task(\n       subagent_type=\"operations-liaison\",\n       description=\"Request system access and equipment\",\n       prompt=\"\"\"\n       Process technical onboarding requirements:\n\n       1. Submit access requests:\n          - Repository access (appropriate permissions)\n          - Development environment setup\n          - Tool access (CI\u002FCD, monitoring, etc.)\n          - Security clearances if needed\n\n       2. Order equipment:\n          - Development laptop (specs for role)\n          - Peripherals (monitors, keyboard, mouse)\n          - Mobile devices if required\n\n       3. Prepare credentials document:\n          - Initial passwords (secure delivery)\n          - Access instructions\n          - Support contacts\n\n       Track request status and escalate blockers.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Faccess-requests.md\n       \"\"\"\n   )\n   ```\n\n3. **Validate Pre-Boarding Readiness**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Validate pre-boarding completion\",\n       prompt=\"\"\"\n       Review pre-boarding status:\n       - Read checklist: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fpre-boarding-checklist.md\n       - Read access status: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Faccess-requests.md\n\n       Validate all items complete or on-track:\n       - System access: READY | PENDING | BLOCKED\n       - Equipment: READY | PENDING | BLOCKED\n       - Documentation: READY | PENDING\n       - Logistics: CONFIRMED | PENDING\n\n       If any BLOCKED items, escalate immediately.\n       Target: 100% complete 2 business days before start.\n\n       Generate readiness report with status and any risks.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fpre-boarding-status.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Pre-boarding initialized for {name}\n⏳ Preparing access and equipment...\n  ✓ System access requests submitted\n  ✓ Equipment ordered (delivery by {date})\n  ✓ Documentation prepared\n✓ Pre-boarding 95% complete (awaiting VPN setup)\n```\n\n### Step 2: Create Personalized Onboarding Plan\n\n**Purpose**: Develop role-specific 90-day plan with clear milestones\n\n**Your Actions**:\n\n1. **Analyze Role and Context**:\n   ```\n   Read available context:\n   - Project intake: .aiwg\u002Fintake\u002Fproject-intake.md\n   - Team roster: .aiwg\u002Fteam\u002Fteam-roster.md\n   - Architecture: .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md\n   ```\n\n2. **Launch Planning Agents** (parallel):\n   ```\n   # Agent 1: Training Coordinator\n   Task(\n       subagent_type=\"training-coordinator\",\n       description=\"Create training schedule for {role}\",\n       prompt=\"\"\"\n       Design training plan for new {role}:\n\n       Week 1: Orientation and Environment\n       - Company\u002Fteam culture and values\n       - Development environment setup\n       - Git workflow and PR process\n       - CI\u002FCD pipeline overview\n       - Basic codebase walkthrough\n\n       Week 2-4: Technical Ramp-Up\n       - Architecture deep dive\n       - Domain knowledge transfer\n       - Coding standards and patterns\n       - Testing strategies\n       - Security best practices\n\n       Month 2: Applied Learning\n       - Pair programming sessions\n       - Code review participation\n       - Feature development with support\n       - Production support shadowing\n\n       Month 3: Independent Contribution\n       - Solo feature ownership\n       - On-call rotation (if applicable)\n       - Process improvement contributions\n\n       Include specific courses, documentation, and hands-on exercises.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Ftraining-schedule.md\n       \"\"\"\n   )\n\n   # Agent 2: Technical Lead\n   Task(\n       subagent_type=\"technical-lead\",\n       description=\"Identify starter tasks and progression\",\n       prompt=\"\"\"\n       Create starter task sequence for {role}:\n\n       Selection criteria:\n       - Self-contained (minimal dependencies)\n       - Low risk (not critical path)\n       - Good learning opportunity\n       - Clear acceptance criteria\n       - Progressive complexity\n\n       Week 1-2 Tasks (Low Complexity):\n       - Documentation improvements\n       - Unit test additions\n       - Bug fixes (minor)\n       - Code refactoring (small scope)\n\n       Week 3-4 Tasks (Medium Complexity):\n       - Small feature implementation\n       - Integration test creation\n       - Performance optimization (isolated)\n       - API endpoint addition\n\n       Month 2+ Tasks (Increasing Complexity):\n       - Cross-component features\n       - System design participation\n       - Architecture improvements\n       - Production issue resolution\n\n       For each task provide:\n       - Task ID and title\n       - Description and context\n       - Acceptance criteria\n       - Estimated effort\n       - Learning objectives\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fstarter-tasks.md\n       \"\"\"\n   )\n\n   # Agent 3: Team Lead\n   Task(\n       subagent_type=\"team-lead\",\n       description=\"Define 30\u002F60\u002F90 day goals\",\n       prompt=\"\"\"\n       Set milestone goals for {name} in {role}:\n\n       30-Day Goals:\n       - Development environment fully functional\n       - Completed 3-5 starter tasks\n       - Participated in team ceremonies\n       - Basic codebase familiarity\n       - First PR merged\n\n       60-Day Goals:\n       - Delivered 1-2 features independently\n       - Active code review participation\n       - Domain knowledge proficiency\n       - Velocity approaching team average\n       - Established working relationships\n\n       90-Day Goals:\n       - Full workload capacity\n       - Mentoring capability\n       - Process improvement contributions\n       - On-call rotation ready\n       - Trusted team member\n\n       Make goals specific, measurable, and role-appropriate.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fmilestone-goals.md\n       \"\"\"\n   )\n   ```\n\n3. **Synthesize Onboarding Plan**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create comprehensive onboarding plan\",\n       prompt=\"\"\"\n       Synthesize onboarding components:\n       - Training schedule: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Ftraining-schedule.md\n       - Starter tasks: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fstarter-tasks.md\n       - Milestone goals: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fmilestone-goals.md\n\n       Create unified 90-day onboarding plan:\n\n       1. Overview\n          - Team member: {name}\n          - Role: {role}\n          - Start date: {start-date}\n          - Buddy: {to be assigned}\n\n       2. Week-by-Week Schedule\n          - Training activities\n          - Task assignments\n          - Check-in meetings\n          - Deliverables\n\n       3. Milestone Checkpoints\n          - 30-day goals and validation\n          - 60-day goals and assessment\n          - 90-day goals and graduation\n\n       4. Support Structure\n          - Buddy responsibilities\n          - Manager 1:1 cadence\n          - Team integration activities\n\n       5. Success Metrics\n          - Quantitative measures\n          - Qualitative feedback\n          - Ramp-up velocity tracking\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fonboarding-plan.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Creating personalized onboarding plan...\n  ✓ Training schedule designed\n  ✓ Starter tasks identified (8 tasks)\n  ✓ 30\u002F60\u002F90 day goals defined\n✓ Onboarding plan complete: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fonboarding-plan.md\n```\n\n### Step 3: Buddy Assignment and Pairing Setup\n\n**Purpose**: Match appropriate buddy and establish support structure\n\n**Your Actions**:\n\n1. **Select and Assign Buddy**:\n   ```\n   Task(\n       subagent_type=\"team-lead\",\n       description=\"Assign buddy for {name}\",\n       prompt=\"\"\"\n       Select appropriate buddy based on:\n       - Domain expertise match\n       - Availability (20% capacity first month)\n       - Mentoring experience\n       - Personality fit\n       - Timezone alignment (if remote)\n\n       Document buddy assignment:\n\n       1. Buddy Selection\n          - Selected: {buddy-name}\n          - Rationale: {why this person}\n          - Backup buddy: {alternate if needed}\n\n       2. Buddy Responsibilities\n          Week 1-4 (Intensive):\n          - Daily pairing (1-2 hours)\n          - Priority code review\n          - On-demand Q&A support\n          - Weekly check-in (30 min)\n\n          Week 5-12 (Ongoing):\n          - 2-3x weekly pairing\n          - Code review with feedback\n          - Monthly progress check\n\n       3. Pairing Schedule\n          - Week 1: Daily 10am-12pm\n          - Week 2-4: MWF 2pm-4pm\n          - Month 2-3: As needed\n\n       4. Knowledge Transfer Topics\n          - Architecture walkthrough\n          - Codebase navigation\n          - Development workflow\n          - Team conventions\n          - Domain concepts\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fbuddy-assignment.md\n       \"\"\"\n   )\n   ```\n\n2. **Notify Buddy and Set Expectations**:\n   ```\n   Task(\n       subagent_type=\"human-resources-coordinator\",\n       description=\"Communicate buddy assignment\",\n       prompt=\"\"\"\n       Create buddy notification and prep materials:\n\n       1. Buddy Notification\n          - Inform selected buddy of assignment\n          - Share onboarding plan\n          - Clarify time commitment\n          - Provide mentoring resources\n\n       2. Capacity Adjustment\n          - Reduce buddy's sprint capacity by 20%\n          - Communicate to project manager\n          - Update team velocity planning\n\n       3. Support Materials\n          - Onboarding checklist for buddy\n          - Common questions and answers\n          - Escalation procedures\n          - Feedback collection process\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fbuddy-prep.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Buddy assigned: {buddy-name}\n✓ Pairing schedule established\n✓ Capacity adjustments made\n```\n\n### Step 4: Execute Onboarding with Progress Tracking\n\n**Purpose**: Monitor daily\u002Fweekly progress and address issues proactively\n\n**Your Actions**:\n\n1. **Week 1 Execution**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Monitor Week 1 onboarding progress\",\n       prompt=\"\"\"\n       Track Week 1 activities for {name}:\n\n       Daily Checklist:\n       Day 1:\n       - [ ] Welcome and introductions\n       - [ ] Equipment setup complete\n       - [ ] Account access verified\n       - [ ] First buddy session\n\n       Day 2-3:\n       - [ ] Development environment setup\n       - [ ] Codebase walkthrough\n       - [ ] First documentation task assigned\n\n       Day 4-5:\n       - [ ] First PR submitted\n       - [ ] Team meeting participation\n       - [ ] Week 1 feedback collected\n\n       Document any blockers or concerns.\n       Escalate access issues immediately.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fweek-1-status.md\n       \"\"\"\n   )\n   ```\n\n2. **Ongoing Progress Monitoring** (weekly):\n   ```\n   Task(\n       subagent_type=\"team-lead\",\n       description=\"Weekly onboarding progress check\",\n       prompt=\"\"\"\n       Assess weekly progress for {name}:\n\n       Review:\n       - Task completion rate\n       - Training attendance\n       - Buddy session feedback\n       - Team integration observations\n\n       Metrics:\n       - Tasks completed: X\u002FY\n       - PRs submitted: count\n       - Code review participation: count\n       - Training modules completed: X\u002FY\n\n       Identify:\n       - Strengths observed\n       - Areas needing support\n       - Pace adjustment needs\n       - Additional resources required\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fweek-{N}-status.md\n       \"\"\"\n   )\n   ```\n\n### Step 5: Conduct 30\u002F60\u002F90 Day Check-Ins\n\n**Purpose**: Formal milestone reviews with feedback and adjustments\n\n**Your Actions**:\n\n1. **30-Day Check-In**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Conduct 30-day check-in for {name}\",\n       prompt=\"\"\"\n       Facilitate 30-day milestone review:\n\n       Attendees: {name}, Manager, Buddy, Technical Lead\n\n       Agenda:\n       1. Goal Review\n          - Environment setup: COMPLETE | PARTIAL | BLOCKED\n          - Starter tasks (3-5): X completed\n          - Team integration: STRONG | GOOD | NEEDS SUPPORT\n\n       2. Feedback Discussion\n          - What's going well?\n          - What challenges exist?\n          - What support is needed?\n\n       3. Performance Assessment\n          - Technical progress: ON TRACK | SLOW | FAST\n          - Team fit: EXCELLENT | GOOD | DEVELOPING\n          - Communication: STRONG | ADEQUATE | NEEDS IMPROVEMENT\n\n       4. Plan Adjustments\n          - Training modifications\n          - Task complexity changes\n          - Support level adjustments\n\n       5. Next 30 Days\n          - Confirm goals\n          - Address concerns\n          - Set expectations\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F30-day-checkin.md\n       \"\"\"\n   )\n   ```\n\n2. **60-Day Check-In**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Conduct 60-day check-in for {name}\",\n       prompt=\"\"\"\n       Facilitate 60-day milestone review:\n\n       Focus: Increasing autonomy and contribution\n\n       Assessment Areas:\n       1. Technical Competence\n          - Feature delivery: {count} completed\n          - Code quality: EXCELLENT | GOOD | DEVELOPING\n          - Problem solving: INDEPENDENT | SUPPORTED | DEPENDENT\n\n       2. Velocity Metrics\n          - Current velocity: X story points\n          - Team average: Y story points\n          - Trajectory: APPROACHING | BELOW | EXCEEDING\n\n       3. Collaboration\n          - Code reviews given: {count}\n          - Design participation: ACTIVE | OBSERVING\n          - Team communication: STRONG | ADEQUATE\n\n       4. Domain Knowledge\n          - Business understanding: STRONG | DEVELOPING\n          - Technical depth: PROFICIENT | LEARNING\n\n       Decision Point:\n       - Ready for full workload? YES | NOT YET\n       - Buddy support reduction? YES | MAINTAIN\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F60-day-checkin.md\n       \"\"\"\n   )\n   ```\n\n3. **90-Day Check-In (Graduation)**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Conduct 90-day graduation review for {name}\",\n       prompt=\"\"\"\n       Facilitate 90-day final review:\n\n       Graduation Criteria:\n       - [ ] Operating at full capacity\n       - [ ] Independently delivering features\n       - [ ] Actively contributing to team\n       - [ ] Ready for on-call (if applicable)\n\n       Final Assessment:\n       1. Overall Performance\n          - Rating: EXCEEDS | MEETS | APPROACHING\n          - Strengths: {list}\n          - Growth areas: {list}\n\n       2. Integration Status\n          - Team member status: FULLY INTEGRATED | NEEDS MORE TIME\n          - Recommendation: GRADUATE | EXTEND SUPPORT\n\n       3. Future Development\n          - Next learning goals\n          - Stretch assignments\n          - Mentoring opportunities\n\n       4. Process Feedback\n          - What worked well in onboarding?\n          - What could improve?\n          - Recommendations for future onboardings\n\n       Decision: ONBOARDING COMPLETE | EXTEND 30 DAYS\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F90-day-checkin.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ 30-day check-in complete: ON TRACK\n✓ 60-day check-in complete: APPROACHING TARGET\n✓ 90-day check-in complete: GRADUATED\n```\n\n### Step 6: Generate Final Onboarding Report\n\n**Purpose**: Summarize complete onboarding journey and capture lessons learned\n\n**Your Actions**:\n\n```\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Generate comprehensive onboarding report\",\n    prompt=\"\"\"\n    Create final onboarding summary for {name}:\n\n    Read all artifacts:\n    - Onboarding plan: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fonboarding-plan.md\n    - Check-ins: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F*-checkin.md\n    - Weekly status: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fweek-*-status.md\n\n    Generate report:\n\n    # Team Onboarding Report\n\n    **Team Member**: {name}\n    **Role**: {role}\n    **Start Date**: {start-date}\n    **Graduation Date**: {90-day-date}\n    **Status**: COMPLETE | EXTENDED | IN PROGRESS\n\n    ## Milestone Achievement\n\n    30-Day Milestone:\n    - Status: ACHIEVED | PARTIAL | MISSED\n    - Key accomplishments: {list}\n\n    60-Day Milestone:\n    - Status: ACHIEVED | PARTIAL | MISSED\n    - Velocity: {X} vs team average {Y}\n\n    90-Day Milestone:\n    - Status: GRADUATED | EXTENDED\n    - Full integration: YES | NO\n\n    ## Metrics Summary\n\n    - Total tasks completed: {count}\n    - Features delivered: {count}\n    - PRs submitted: {count}\n    - Code reviews performed: {count}\n    - Training modules completed: {X}\u002F{Y}\n    - Ramp-up velocity: {FAST | NORMAL | SLOW}\n\n    ## Buddy Relationship\n\n    - Buddy: {buddy-name}\n    - Total pairing hours: {hours}\n    - Effectiveness: {rating and feedback}\n\n    ## Strengths Demonstrated\n    - {strength 1}\n    - {strength 2}\n    - {strength 3}\n\n    ## Development Areas\n    - {area 1}\n    - {area 2}\n\n    ## Process Improvements\n\n    Based on this onboarding:\n    - {improvement 1}\n    - {improvement 2}\n    - {improvement 3}\n\n    ## Recommendations\n\n    For {name}:\n    - Next development goals\n    - Suggested projects\u002Ffeatures\n    - Mentoring opportunities\n\n    For future onboardings:\n    - Process adjustments\n    - Resource additions\n    - Timeline modifications\n\n    Output: .aiwg\u002Freports\u002Fonboarding-complete-{name}.md\n    \"\"\"\n)\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Pre-boarding 100% complete before start date\n- [ ] Buddy assigned and prepared\n- [ ] Onboarding plan reviewed and approved\n- [ ] All milestone check-ins conducted\n- [ ] Graduation criteria met or extension justified\n- [ ] Feedback collected and documented\n- [ ] Process improvements identified\n\n## User Communication\n\n**At start**: Confirm understanding and timeline\n\n```\nUnderstood. I'll orchestrate onboarding for {name} starting {date}.\n\nThis will include:\n- Pre-boarding preparation (access, equipment, docs)\n- 90-day personalized onboarding plan\n- Buddy assignment and pairing schedule\n- Starter tasks with progressive complexity\n- 30\u002F60\u002F90 day milestone check-ins\n- Progress tracking and reporting\n\nExpected timeline: 90 days total, with weekly progress updates.\n\nStarting pre-boarding preparation...\n```\n\n**During**: Regular status updates\n\n```\nWeek 1 Status:\n✓ Day 1: Welcome complete, environment 80% setup\n✓ Day 2: First PR submitted (documentation fix)\n⏳ Day 3: Codebase walkthrough with buddy\n⚠️ Blocker: CI\u002FCD access pending (escalated)\n```\n\n**At milestones**: Detailed checkpoint summaries\n\n```\n30-Day Check-In Complete:\n- Status: ON TRACK\n- Tasks completed: 4\u002F5\n- First feature delivered\n- Team integration: STRONG\n- Next focus: Increase task complexity\n```\n\n## Error Handling\n\n**Access Delays**:\n```\n⚠️ System access delayed - impacting onboarding\n\nMissing access:\n- {system}: Expected {date}, now {new-date}\n\nMitigation:\n- Buddy providing screen-share access\n- Read-only access granted temporarily\n- Adjusting task sequence\n\nImpact: Minimal if resolved within 48 hours\n```\n\n**Buddy Unavailable**:\n```\n⚠️ Buddy unavailable due to {reason}\n\nAction taken:\n- Backup buddy activated: {backup-name}\n- Knowledge transfer session scheduled\n- Pairing schedule adjusted\n\nNo impact to onboarding timeline expected.\n```\n\n**Slow Progress**:\n```\n⚠️ 30-day milestone partially met\n\nGaps:\n- Tasks completed: 2\u002F5 (target: 3-5)\n- PR velocity below target\n\nAdjustments:\n- Increased buddy pairing time\n- Simplified task complexity\n- Additional training scheduled\n\nReviewing progress weekly for improvement.\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] New team member fully productive by day 90\n- [ ] All milestones achieved or explicitly adjusted\n- [ ] Positive feedback from team member and buddy\n- [ ] No critical knowledge gaps identified\n- [ ] Team integration successful\n- [ ] Process improvements documented\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Team Roster: team roster fields in this skill\n- Onboarding Plan: onboarding plan fields in this skill\n- Buddy Assignment: buddy assignment fields in this skill\n- Training Schedule: training schedule fields in this skill\n- Work Package: `templates\u002Fmanagement\u002Fwork-package-card.md`\n- Milestone Checklist: milestone checklist in this skill\n\n**Related Flows**:\n- `flow-team-coordination` - Ongoing team management\n- `flow-knowledge-transfer` - Deep technical knowledge sharing\n- `flow-training-certification` - Formal training programs\n\n**Supporting Documents**:\n- `docs\u002Fteam-onboarding-best-practices.md`\n- `docs\u002Fbuddy-system-guide.md`\n- `docs\u002Fremote-onboarding-adjustments.md`","> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-team-onboarding.playbook.yaml` (source of truth for the step\n> sequence + gates). This SKILL.md remains the discoverable trigger surface and prose\n> reference. See epic #1534.\n\n# Team Onboarding Flow\n\n**You are the Core Orchestrator** for team member onboarding, ensuring systematic integration with proper knowledge transfer and milestone-based progression.\n\n## Your Role\n\n**You orchestrate multi-agent workflows. You do NOT execute bash scripts.**\n\nWhen the user requests this flow (via natural language or explicit command):\n\n1. **Interpret the request** and confirm understanding\n2. **Read this template** as your orchestration guide\n3. **Extract agent assignments** and workflow steps\n4. **Delegate agents with the current provider-native orchestration mechanism** in the correct sequence\n5. **Synthesize results** and track progress\n6. **Report completion** with onboarding status\n\n## Onboarding Process Overview\n\n**Purpose**: Systematically integrate new team members with structured ramp-up, knowledge transfer, and milestone-based validation\n\n**Duration**: 90 days (30\u002F60\u002F90 day milestones)\n\n**Success Criteria**:\n- Pre-boarding checklist 100% complete by start date\n- Buddy assigned with pairing cadence established\n- 30\u002F60\u002F90 day milestones achieved on schedule\n- Full productivity reached by day 90\n- Onboarding feedback collected for process improvement\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Onboard [name] as [role]\"\n- \"Add team member [name]\"\n- \"New team member [name] starting [date]\"\n- \"Onboard new developer\"\n- \"Add [name] to the team\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Parameter Handling\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor onboarding focus\n\n**Examples**:\n```\n--guidance \"Technical architect role, focus on security and infrastructure\"\n--guidance \"Junior developer, needs extra mentorship and pairing\"\n--guidance \"Remote team member in different timezone, coordinate async\"\n--guidance \"Fast-track onboarding for urgent project needs\"\n```\n\n**How to Apply**:\n- Parse guidance for role specifics (seniority, domain focus)\n- Adjust buddy assignment (match expertise areas)\n- Modify training intensity (junior vs senior needs)\n- Adapt communication approach (remote vs local)\n\n### --interactive Parameter\n\n**Purpose**: You ask 6 strategic questions to understand onboarding needs\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 6 strategic questions to tailor this onboarding flow:\n\nQ1: What are your top priorities for this new team member?\n    (e.g., specific skills, project ownership, team collaboration)\n\nQ2: What are your biggest constraints for onboarding?\n    (e.g., timeline, buddy availability, remote coordination)\n\nQ3: What risks concern you most for this onboarding?\n    (e.g., skill gaps, team fit, ramp-up speed)\n\nQ4: What's your team's experience level with onboarding?\n    (helps calibrate support level and documentation needs)\n\nQ5: What's your target timeline for full productivity?\n    (typical: 90 days, urgent: 30-60 days)\n\nQ6: Are there compliance or security clearance requirements?\n    (e.g., background checks, training certifications)\n\nBased on your answers, I'll adjust:\n- Buddy selection and pairing intensity\n- Training schedule and focus areas\n- Milestone targets and check-in frequency\n- Documentation and access requirements\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance for execution\n\n## Artifacts to Generate\n\n**Primary Deliverables**:\n- **Pre-Boarding Checklist**: System access, equipment, documentation → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fpre-boarding-checklist.md`\n- **Onboarding Plan**: Personalized 90-day plan → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fonboarding-plan.md`\n- **Buddy Assignment**: Buddy responsibilities and schedule → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fbuddy-assignment.md`\n- **Starter Tasks**: Sequenced tasks with acceptance criteria → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fstarter-tasks.md`\n- **30-Day Check-In Report**: Milestone review → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F30-day-checkin.md`\n- **60-Day Check-In Report**: Performance assessment → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F60-day-checkin.md`\n- **90-Day Check-In Report**: Full integration validation → `.aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F90-day-checkin.md`\n- **Onboarding Status Report**: Current progress tracker → `.aiwg\u002Freports\u002Fonboarding-status-{name}.md`\n\n**Supporting Artifacts**:\n- Training schedule and materials\n- Knowledge transfer documentation\n- Feedback collection forms\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Pre-Boarding Preparation\n\n**Purpose**: Ensure all systems, equipment, and documentation ready before start date\n\n**Your Actions**:\n\n1. **Initialize Onboarding Workspace**:\n   ```\n   Create directory structure:\n   .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F\n   ├── pre-boarding\u002F\n   ├── training\u002F\n   ├── check-ins\u002F\n   └── feedback\u002F\n   ```\n\n2. **Launch Pre-Boarding Agents** (parallel):\n   ```\n   # Agent 1: HR Coordinator\n   Task(\n       subagent_type=\"human-resources-coordinator\",\n       description=\"Prepare pre-boarding checklist and paperwork\",\n       prompt=\"\"\"\n       Create pre-boarding checklist for new team member:\n       - Name: {name}\n       - Role: {role}\n       - Start Date: {start-date}\n\n       Document requirements:\n       1. System Access\n          - [ ] Git repository access (read\u002Fwrite)\n          - [ ] CI\u002FCD pipeline access\n          - [ ] Issue tracker account\n          - [ ] Monitoring\u002Flogging tools\n          - [ ] Communication channels (Slack, email lists)\n          - [ ] VPN credentials\n          - [ ] SSO\u002FMFA setup\n\n       2. Equipment\n          - [ ] Laptop provisioned with OS and dev tools\n          - [ ] Monitor(s) and peripherals\n          - [ ] Security badge\u002Faccess card\n\n       3. Documentation\n          - [ ] Project README and CLAUDE.md\n          - [ ] Architecture documentation\n          - [ ] Runbooks and procedures\n          - [ ] Team conventions\n\n       4. First Day Logistics\n          - [ ] Welcome email with agenda\n          - [ ] Meeting invites sent\n          - [ ] Workspace prepared\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fpre-boarding-checklist.md\n       \"\"\"\n   )\n\n   # Agent 2: Operations Liaison\n   Task(\n       subagent_type=\"operations-liaison\",\n       description=\"Request system access and equipment\",\n       prompt=\"\"\"\n       Process technical onboarding requirements:\n\n       1. Submit access requests:\n          - Repository access (appropriate permissions)\n          - Development environment setup\n          - Tool access (CI\u002FCD, monitoring, etc.)\n          - Security clearances if needed\n\n       2. Order equipment:\n          - Development laptop (specs for role)\n          - Peripherals (monitors, keyboard, mouse)\n          - Mobile devices if required\n\n       3. Prepare credentials document:\n          - Initial passwords (secure delivery)\n          - Access instructions\n          - Support contacts\n\n       Track request status and escalate blockers.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Faccess-requests.md\n       \"\"\"\n   )\n   ```\n\n3. **Validate Pre-Boarding Readiness**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Validate pre-boarding completion\",\n       prompt=\"\"\"\n       Review pre-boarding status:\n       - Read checklist: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fpre-boarding-checklist.md\n       - Read access status: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Faccess-requests.md\n\n       Validate all items complete or on-track:\n       - System access: READY | PENDING | BLOCKED\n       - Equipment: READY | PENDING | BLOCKED\n       - Documentation: READY | PENDING\n       - Logistics: CONFIRMED | PENDING\n\n       If any BLOCKED items, escalate immediately.\n       Target: 100% complete 2 business days before start.\n\n       Generate readiness report with status and any risks.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fpre-boarding-status.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Pre-boarding initialized for {name}\n⏳ Preparing access and equipment...\n  ✓ System access requests submitted\n  ✓ Equipment ordered (delivery by {date})\n  ✓ Documentation prepared\n✓ Pre-boarding 95% complete (awaiting VPN setup)\n```\n\n### Step 2: Create Personalized Onboarding Plan\n\n**Purpose**: Develop role-specific 90-day plan with clear milestones\n\n**Your Actions**:\n\n1. **Analyze Role and Context**:\n   ```\n   Read available context:\n   - Project intake: .aiwg\u002Fintake\u002Fproject-intake.md\n   - Team roster: .aiwg\u002Fteam\u002Fteam-roster.md\n   - Architecture: .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md\n   ```\n\n2. **Launch Planning Agents** (parallel):\n   ```\n   # Agent 1: Training Coordinator\n   Task(\n       subagent_type=\"training-coordinator\",\n       description=\"Create training schedule for {role}\",\n       prompt=\"\"\"\n       Design training plan for new {role}:\n\n       Week 1: Orientation and Environment\n       - Company\u002Fteam culture and values\n       - Development environment setup\n       - Git workflow and PR process\n       - CI\u002FCD pipeline overview\n       - Basic codebase walkthrough\n\n       Week 2-4: Technical Ramp-Up\n       - Architecture deep dive\n       - Domain knowledge transfer\n       - Coding standards and patterns\n       - Testing strategies\n       - Security best practices\n\n       Month 2: Applied Learning\n       - Pair programming sessions\n       - Code review participation\n       - Feature development with support\n       - Production support shadowing\n\n       Month 3: Independent Contribution\n       - Solo feature ownership\n       - On-call rotation (if applicable)\n       - Process improvement contributions\n\n       Include specific courses, documentation, and hands-on exercises.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Ftraining-schedule.md\n       \"\"\"\n   )\n\n   # Agent 2: Technical Lead\n   Task(\n       subagent_type=\"technical-lead\",\n       description=\"Identify starter tasks and progression\",\n       prompt=\"\"\"\n       Create starter task sequence for {role}:\n\n       Selection criteria:\n       - Self-contained (minimal dependencies)\n       - Low risk (not critical path)\n       - Good learning opportunity\n       - Clear acceptance criteria\n       - Progressive complexity\n\n       Week 1-2 Tasks (Low Complexity):\n       - Documentation improvements\n       - Unit test additions\n       - Bug fixes (minor)\n       - Code refactoring (small scope)\n\n       Week 3-4 Tasks (Medium Complexity):\n       - Small feature implementation\n       - Integration test creation\n       - Performance optimization (isolated)\n       - API endpoint addition\n\n       Month 2+ Tasks (Increasing Complexity):\n       - Cross-component features\n       - System design participation\n       - Architecture improvements\n       - Production issue resolution\n\n       For each task provide:\n       - Task ID and title\n       - Description and context\n       - Acceptance criteria\n       - Estimated effort\n       - Learning objectives\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fstarter-tasks.md\n       \"\"\"\n   )\n\n   # Agent 3: Team Lead\n   Task(\n       subagent_type=\"team-lead\",\n       description=\"Define 30\u002F60\u002F90 day goals\",\n       prompt=\"\"\"\n       Set milestone goals for {name} in {role}:\n\n       30-Day Goals:\n       - Development environment fully functional\n       - Completed 3-5 starter tasks\n       - Participated in team ceremonies\n       - Basic codebase familiarity\n       - First PR merged\n\n       60-Day Goals:\n       - Delivered 1-2 features independently\n       - Active code review participation\n       - Domain knowledge proficiency\n       - Velocity approaching team average\n       - Established working relationships\n\n       90-Day Goals:\n       - Full workload capacity\n       - Mentoring capability\n       - Process improvement contributions\n       - On-call rotation ready\n       - Trusted team member\n\n       Make goals specific, measurable, and role-appropriate.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fmilestone-goals.md\n       \"\"\"\n   )\n   ```\n\n3. **Synthesize Onboarding Plan**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create comprehensive onboarding plan\",\n       prompt=\"\"\"\n       Synthesize onboarding components:\n       - Training schedule: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Ftraining-schedule.md\n       - Starter tasks: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fstarter-tasks.md\n       - Milestone goals: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fmilestone-goals.md\n\n       Create unified 90-day onboarding plan:\n\n       1. Overview\n          - Team member: {name}\n          - Role: {role}\n          - Start date: {start-date}\n          - Buddy: {to be assigned}\n\n       2. Week-by-Week Schedule\n          - Training activities\n          - Task assignments\n          - Check-in meetings\n          - Deliverables\n\n       3. Milestone Checkpoints\n          - 30-day goals and validation\n          - 60-day goals and assessment\n          - 90-day goals and graduation\n\n       4. Support Structure\n          - Buddy responsibilities\n          - Manager 1:1 cadence\n          - Team integration activities\n\n       5. Success Metrics\n          - Quantitative measures\n          - Qualitative feedback\n          - Ramp-up velocity tracking\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fonboarding-plan.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Creating personalized onboarding plan...\n  ✓ Training schedule designed\n  ✓ Starter tasks identified (8 tasks)\n  ✓ 30\u002F60\u002F90 day goals defined\n✓ Onboarding plan complete: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fonboarding-plan.md\n```\n\n### Step 3: Buddy Assignment and Pairing Setup\n\n**Purpose**: Match appropriate buddy and establish support structure\n\n**Your Actions**:\n\n1. **Select and Assign Buddy**:\n   ```\n   Task(\n       subagent_type=\"team-lead\",\n       description=\"Assign buddy for {name}\",\n       prompt=\"\"\"\n       Select appropriate buddy based on:\n       - Domain expertise match\n       - Availability (20% capacity first month)\n       - Mentoring experience\n       - Personality fit\n       - Timezone alignment (if remote)\n\n       Document buddy assignment:\n\n       1. Buddy Selection\n          - Selected: {buddy-name}\n          - Rationale: {why this person}\n          - Backup buddy: {alternate if needed}\n\n       2. Buddy Responsibilities\n          Week 1-4 (Intensive):\n          - Daily pairing (1-2 hours)\n          - Priority code review\n          - On-demand Q&A support\n          - Weekly check-in (30 min)\n\n          Week 5-12 (Ongoing):\n          - 2-3x weekly pairing\n          - Code review with feedback\n          - Monthly progress check\n\n       3. Pairing Schedule\n          - Week 1: Daily 10am-12pm\n          - Week 2-4: MWF 2pm-4pm\n          - Month 2-3: As needed\n\n       4. Knowledge Transfer Topics\n          - Architecture walkthrough\n          - Codebase navigation\n          - Development workflow\n          - Team conventions\n          - Domain concepts\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fbuddy-assignment.md\n       \"\"\"\n   )\n   ```\n\n2. **Notify Buddy and Set Expectations**:\n   ```\n   Task(\n       subagent_type=\"human-resources-coordinator\",\n       description=\"Communicate buddy assignment\",\n       prompt=\"\"\"\n       Create buddy notification and prep materials:\n\n       1. Buddy Notification\n          - Inform selected buddy of assignment\n          - Share onboarding plan\n          - Clarify time commitment\n          - Provide mentoring resources\n\n       2. Capacity Adjustment\n          - Reduce buddy's sprint capacity by 20%\n          - Communicate to project manager\n          - Update team velocity planning\n\n       3. Support Materials\n          - Onboarding checklist for buddy\n          - Common questions and answers\n          - Escalation procedures\n          - Feedback collection process\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fbuddy-prep.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Buddy assigned: {buddy-name}\n✓ Pairing schedule established\n✓ Capacity adjustments made\n```\n\n### Step 4: Execute Onboarding with Progress Tracking\n\n**Purpose**: Monitor daily\u002Fweekly progress and address issues proactively\n\n**Your Actions**:\n\n1. **Week 1 Execution**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Monitor Week 1 onboarding progress\",\n       prompt=\"\"\"\n       Track Week 1 activities for {name}:\n\n       Daily Checklist:\n       Day 1:\n       - [ ] Welcome and introductions\n       - [ ] Equipment setup complete\n       - [ ] Account access verified\n       - [ ] First buddy session\n\n       Day 2-3:\n       - [ ] Development environment setup\n       - [ ] Codebase walkthrough\n       - [ ] First documentation task assigned\n\n       Day 4-5:\n       - [ ] First PR submitted\n       - [ ] Team meeting participation\n       - [ ] Week 1 feedback collected\n\n       Document any blockers or concerns.\n       Escalate access issues immediately.\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fweek-1-status.md\n       \"\"\"\n   )\n   ```\n\n2. **Ongoing Progress Monitoring** (weekly):\n   ```\n   Task(\n       subagent_type=\"team-lead\",\n       description=\"Weekly onboarding progress check\",\n       prompt=\"\"\"\n       Assess weekly progress for {name}:\n\n       Review:\n       - Task completion rate\n       - Training attendance\n       - Buddy session feedback\n       - Team integration observations\n\n       Metrics:\n       - Tasks completed: X\u002FY\n       - PRs submitted: count\n       - Code review participation: count\n       - Training modules completed: X\u002FY\n\n       Identify:\n       - Strengths observed\n       - Areas needing support\n       - Pace adjustment needs\n       - Additional resources required\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fweek-{N}-status.md\n       \"\"\"\n   )\n   ```\n\n### Step 5: Conduct 30\u002F60\u002F90 Day Check-Ins\n\n**Purpose**: Formal milestone reviews with feedback and adjustments\n\n**Your Actions**:\n\n1. **30-Day Check-In**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Conduct 30-day check-in for {name}\",\n       prompt=\"\"\"\n       Facilitate 30-day milestone review:\n\n       Attendees: {name}, Manager, Buddy, Technical Lead\n\n       Agenda:\n       1. Goal Review\n          - Environment setup: COMPLETE | PARTIAL | BLOCKED\n          - Starter tasks (3-5): X completed\n          - Team integration: STRONG | GOOD | NEEDS SUPPORT\n\n       2. Feedback Discussion\n          - What's going well?\n          - What challenges exist?\n          - What support is needed?\n\n       3. Performance Assessment\n          - Technical progress: ON TRACK | SLOW | FAST\n          - Team fit: EXCELLENT | GOOD | DEVELOPING\n          - Communication: STRONG | ADEQUATE | NEEDS IMPROVEMENT\n\n       4. Plan Adjustments\n          - Training modifications\n          - Task complexity changes\n          - Support level adjustments\n\n       5. Next 30 Days\n          - Confirm goals\n          - Address concerns\n          - Set expectations\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F30-day-checkin.md\n       \"\"\"\n   )\n   ```\n\n2. **60-Day Check-In**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Conduct 60-day check-in for {name}\",\n       prompt=\"\"\"\n       Facilitate 60-day milestone review:\n\n       Focus: Increasing autonomy and contribution\n\n       Assessment Areas:\n       1. Technical Competence\n          - Feature delivery: {count} completed\n          - Code quality: EXCELLENT | GOOD | DEVELOPING\n          - Problem solving: INDEPENDENT | SUPPORTED | DEPENDENT\n\n       2. Velocity Metrics\n          - Current velocity: X story points\n          - Team average: Y story points\n          - Trajectory: APPROACHING | BELOW | EXCEEDING\n\n       3. Collaboration\n          - Code reviews given: {count}\n          - Design participation: ACTIVE | OBSERVING\n          - Team communication: STRONG | ADEQUATE\n\n       4. Domain Knowledge\n          - Business understanding: STRONG | DEVELOPING\n          - Technical depth: PROFICIENT | LEARNING\n\n       Decision Point:\n       - Ready for full workload? YES | NOT YET\n       - Buddy support reduction? YES | MAINTAIN\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F60-day-checkin.md\n       \"\"\"\n   )\n   ```\n\n3. **90-Day Check-In (Graduation)**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Conduct 90-day graduation review for {name}\",\n       prompt=\"\"\"\n       Facilitate 90-day final review:\n\n       Graduation Criteria:\n       - [ ] Operating at full capacity\n       - [ ] Independently delivering features\n       - [ ] Actively contributing to team\n       - [ ] Ready for on-call (if applicable)\n\n       Final Assessment:\n       1. Overall Performance\n          - Rating: EXCEEDS | MEETS | APPROACHING\n          - Strengths: {list}\n          - Growth areas: {list}\n\n       2. Integration Status\n          - Team member status: FULLY INTEGRATED | NEEDS MORE TIME\n          - Recommendation: GRADUATE | EXTEND SUPPORT\n\n       3. Future Development\n          - Next learning goals\n          - Stretch assignments\n          - Mentoring opportunities\n\n       4. Process Feedback\n          - What worked well in onboarding?\n          - What could improve?\n          - Recommendations for future onboardings\n\n       Decision: ONBOARDING COMPLETE | EXTEND 30 DAYS\n\n       Output: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F90-day-checkin.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ 30-day check-in complete: ON TRACK\n✓ 60-day check-in complete: APPROACHING TARGET\n✓ 90-day check-in complete: GRADUATED\n```\n\n### Step 6: Generate Final Onboarding Report\n\n**Purpose**: Summarize complete onboarding journey and capture lessons learned\n\n**Your Actions**:\n\n```\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Generate comprehensive onboarding report\",\n    prompt=\"\"\"\n    Create final onboarding summary for {name}:\n\n    Read all artifacts:\n    - Onboarding plan: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fonboarding-plan.md\n    - Check-ins: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002F*-checkin.md\n    - Weekly status: .aiwg\u002Fteam\u002Fonboarding\u002F{name}\u002Fweek-*-status.md\n\n    Generate report:\n\n    # Team Onboarding Report\n\n    **Team Member**: {name}\n    **Role**: {role}\n    **Start Date**: {start-date}\n    **Graduation Date**: {90-day-date}\n    **Status**: COMPLETE | EXTENDED | IN PROGRESS\n\n    ## Milestone Achievement\n\n    30-Day Milestone:\n    - Status: ACHIEVED | PARTIAL | MISSED\n    - Key accomplishments: {list}\n\n    60-Day Milestone:\n    - Status: ACHIEVED | PARTIAL | MISSED\n    - Velocity: {X} vs team average {Y}\n\n    90-Day Milestone:\n    - Status: GRADUATED | EXTENDED\n    - Full integration: YES | NO\n\n    ## Metrics Summary\n\n    - Total tasks completed: {count}\n    - Features delivered: {count}\n    - PRs submitted: {count}\n    - Code reviews performed: {count}\n    - Training modules completed: {X}\u002F{Y}\n    - Ramp-up velocity: {FAST | NORMAL | SLOW}\n\n    ## Buddy Relationship\n\n    - Buddy: {buddy-name}\n    - Total pairing hours: {hours}\n    - Effectiveness: {rating and feedback}\n\n    ## Strengths Demonstrated\n    - {strength 1}\n    - {strength 2}\n    - {strength 3}\n\n    ## Development Areas\n    - {area 1}\n    - {area 2}\n\n    ## Process Improvements\n\n    Based on this onboarding:\n    - {improvement 1}\n    - {improvement 2}\n    - {improvement 3}\n\n    ## Recommendations\n\n    For {name}:\n    - Next development goals\n    - Suggested projects\u002Ffeatures\n    - Mentoring opportunities\n\n    For future onboardings:\n    - Process adjustments\n    - Resource additions\n    - Timeline modifications\n\n    Output: .aiwg\u002Freports\u002Fonboarding-complete-{name}.md\n    \"\"\"\n)\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Pre-boarding 100% complete before start date\n- [ ] Buddy assigned and prepared\n- [ ] Onboarding plan reviewed and approved\n- [ ] All milestone check-ins conducted\n- [ ] Graduation criteria met or extension justified\n- [ ] Feedback collected and documented\n- [ ] Process improvements identified\n\n## User Communication\n\n**At start**: Confirm understanding and timeline\n\n```\nUnderstood. I'll orchestrate onboarding for {name} starting {date}.\n\nThis will include:\n- Pre-boarding preparation (access, equipment, docs)\n- 90-day personalized onboarding plan\n- Buddy assignment and pairing schedule\n- Starter tasks with progressive complexity\n- 30\u002F60\u002F90 day milestone check-ins\n- Progress tracking and reporting\n\nExpected timeline: 90 days total, with weekly progress updates.\n\nStarting pre-boarding preparation...\n```\n\n**During**: Regular status updates\n\n```\nWeek 1 Status:\n✓ Day 1: Welcome complete, environment 80% setup\n✓ Day 2: First PR submitted (documentation fix)\n⏳ Day 3: Codebase walkthrough with buddy\n⚠️ Blocker: CI\u002FCD access pending (escalated)\n```\n\n**At milestones**: Detailed checkpoint summaries\n\n```\n30-Day Check-In Complete:\n- Status: ON TRACK\n- Tasks completed: 4\u002F5\n- First feature delivered\n- Team integration: STRONG\n- Next focus: Increase task complexity\n```\n\n## Error Handling\n\n**Access Delays**:\n```\n⚠️ System access delayed - impacting onboarding\n\nMissing access:\n- {system}: Expected {date}, now {new-date}\n\nMitigation:\n- Buddy providing screen-share access\n- Read-only access granted temporarily\n- Adjusting task sequence\n\nImpact: Minimal if resolved within 48 hours\n```\n\n**Buddy Unavailable**:\n```\n⚠️ Buddy unavailable due to {reason}\n\nAction taken:\n- Backup buddy activated: {backup-name}\n- Knowledge transfer session scheduled\n- Pairing schedule adjusted\n\nNo impact to onboarding timeline expected.\n```\n\n**Slow Progress**:\n```\n⚠️ 30-day milestone partially met\n\nGaps:\n- Tasks completed: 2\u002F5 (target: 3-5)\n- PR velocity below target\n\nAdjustments:\n- Increased buddy pairing time\n- Simplified task complexity\n- Additional training scheduled\n\nReviewing progress weekly for improvement.\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] New team member fully productive by day 90\n- [ ] All milestones achieved or explicitly adjusted\n- [ ] Positive feedback from team member and buddy\n- [ ] No critical knowledge gaps identified\n- [ ] Team integration successful\n- [ ] Process improvements documented\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Team Roster: team roster fields in this skill\n- Onboarding Plan: onboarding plan fields in this skill\n- Buddy Assignment: buddy assignment fields in this skill\n- Training Schedule: training schedule fields in this skill\n- Work Package: `templates\u002Fmanagement\u002Fwork-package-card.md`\n- Milestone Checklist: milestone checklist in this skill\n\n**Related Flows**:\n- `flow-team-coordination` - Ongoing team management\n- `flow-knowledge-transfer` - Deep technical knowledge sharing\n- `flow-training-certification` - Formal training programs\n\n**Supporting Documents**:\n- `docs\u002Fteam-onboarding-best-practices.md`\n- `docs\u002Fbuddy-system-guide.md`\n- `docs\u002Fremote-onboarding-adjustments.md`",{"name":5,"namespace":54,"platforms":55,"commandHint":57,"description":7},"aiwg",[56],"all",{"model":37,"category":58,"modelRole":41,"modelTier":35,"allowedTools":59,"argumentHint":60,"orchestration":61},"sdlc-orchestration","Task, Read, Write, Glob, TodoWrite","\u003Cteam-member-name> [role] [start-date] [--guidance \"text\"] [--interactive]",true,"main","a602706fc62ff1cfcb18001358ac39647b08acf5","agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Fflow-team-onboarding",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-11 08:11:25",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":61},[74,77,80],{"tool":75,"command":76},"npx","npx skills add jmagly\u002Faiwg --skill flow-team-onboarding",{"tool":78,"command":79},"bunx","bunx skills add jmagly\u002Faiwg --skill flow-team-onboarding",{"tool":81,"command":82},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill flow-team-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Fflow-team-onboarding\u002FSKILL.md",[],[86,113,136,142,149,162],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":93,"publishedAt":49},"01M70QA0BSYJ49EES9V4RE8QH1","host-hardening","Read-only system hardening baseline and plan-first host hardening recommendations for SSH, Docker bind addresses, firewall persistence, datastores, exporters and audit retention.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[92],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[94,95,96,44,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"host","host hardening","hardening","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":123,"publishedAt":49},"01M70PNT2Z4HMZPRBTAF6073NN","exposure-analysis","Read-only firewall analysis and effective host exposure reconstruction for Docker published ports, UFW bypass, stale rules, CDN scope, IPv6 asymmetry and external probe allowlists.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fforensics\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[119,122],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[124,125,126,44,127,101,128,129,103,130,94,131,105,132,133,108,109,134,135,43],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator",{"skillNo":137,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":49},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[140],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[96,94,95,104,44,112,99,98,107,100,101,102,103,111,105,106,97,108,109,110],{"skillNo":143,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":148,"publishedAt":49},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[146,147],{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[125,124,108,127,101,128,103,126,94,131,105,132,133,44,109,130,129,134,135,43],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":49},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[155],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[157,158,159,160,36,161],"fixture skill","fixture","rule","delivery","exercise",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":49},"01M6CB4AVK1W76MFMPP0JP32CJ","pi-local","Pi-local duplicate-precedence fixture.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fproviders\u002Fpi\u002Fproject\u002F.pi\u002Fskills\u002Fpi-local\u002FSKILL.md",[168],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[170,171,132,172,158],"pi","pi local","duplicate"]