← Back to list

team-onboarding
by mguttmann
Autonomous Organization Framework - A complete system for AI-assisted software development with Claude Code
⭐ 0🍴 0📅 Jan 25, 2026
SKILL.md
name: team-onboarding description: Onboarding new team members effectively
Team Onboarding
Strukturierter Prozess für effektives Onboarding neuer Team-Mitglieder.
Onboarding Timeline
┌─────────────────────────────────────────────────────────────────────────────┐
│ │
│ PRE-DAY 1: PREPARATION │
│ └── Accounts, Equipment, Buddy assignment │
│ │
│ DAY 1: WELCOME │
│ └── Setup, Introductions, First PR │
│ │
│ WEEK 1: ORIENTATION │
│ └── Codebase tour, Process overview, First tasks │
│ │
│ WEEK 2-4: RAMPING │
│ └── Increasing complexity, Pairing, Feedback │
│ │
│ MONTH 2-3: INDEPENDENCE │
│ └── Own features, Reduced support, Full contributor │
│ │
│ DAY 90: GRADUATION │
│ └── Retro, Full autonomy, Potential buddy role │
│ │
└─────────────────────────────────────────────────────────────────────────────┘
Pre-Day 1 Checklist
## Onboarding Prep: [New Hire Name]
### Manager Tasks
- [ ] Announce hire to team
- [ ] Assign onboarding buddy
- [ ] Schedule 1:1s for first week
- [ ] Prepare first tasks (starter issues)
### IT/Admin Tasks
- [ ] Email account created
- [ ] Slack/Teams access
- [ ] GitHub/GitLab access
- [ ] Cloud accounts (AWS/GCP/Azure)
- [ ] VPN access
- [ ] Hardware ordered/ready
- [ ] Building access/badge
### Documentation Ready
- [ ] Onboarding guide link ready
- [ ] Team wiki access
- [ ] Architecture docs available
- [ ] Process documentation current
### First Day Prepared
- [ ] Welcome meeting scheduled
- [ ] Lunch/coffee with team planned
- [ ] Desk/workspace ready
- [ ] Welcome message drafted
Day 1 Agenda
## Day 1: [Date]
### Morning (Setup)
| Time | Activity | With | Duration |
|------|----------|------|----------|
| 9:00 | Welcome & Admin | Manager | 30 min |
| 9:30 | IT Setup | IT/Self | 1 hour |
| 10:30 | Coffee Break | Buddy | 15 min |
| 10:45 | Tool Setup | Buddy | 1 hour |
| 12:00 | Team Lunch | Team | 1 hour |
### Afternoon (First Steps)
| Time | Activity | With | Duration |
|------|----------|------|----------|
| 13:00 | Codebase Overview | Buddy | 1 hour |
| 14:00 | Clone & Run | Self/Buddy | 1 hour |
| 15:00 | First PR (Readme/Typo) | Self | 1 hour |
| 16:00 | Day 1 Wrap-up | Manager | 30 min |
### Day 1 Goals
- [ ] All accounts working
- [ ] Dev environment running
- [ ] First PR submitted
- [ ] Met the team
- [ ] Knows who to ask for help
Week 1 Plan
## Week 1: Orientation
### Goals
- [ ] Understand product/domain
- [ ] Navigate codebase
- [ ] Complete 2-3 starter issues
- [ ] Know team processes
### Daily Themes
| Day | Focus | Activities |
|-----|-------|------------|
| Mon | Setup | Environment, first PR |
| Tue | Product | Product demo, user journey |
| Wed | Architecture | System overview, key components |
| Thu | Process | Git workflow, CI/CD, reviews |
| Fri | Practice | Starter issues, questions |
### Learning Resources
| Topic | Resource | Priority |
|-------|----------|----------|
| Product | [Product docs/demo] | High |
| Architecture | [Architecture docs] | High |
| Codebase | [Code tour/README] | High |
| Processes | [Team wiki] | Medium |
| History | [Key decisions/ADRs] | Low |
### Starter Issues
| Issue | Complexity | Purpose |
|-------|------------|---------|
| [#123 Fix typo] | Easy | First contribution |
| [#124 Add test] | Easy | Understand testing |
| [#125 Small feature] | Medium | End-to-end flow |
Onboarding Checklist
## Onboarding Checklist: [Name]
Start Date: [Date]
Manager: [Name]
Buddy: [Name]
### Week 1: Foundation
- [ ] Dev environment working
- [ ] Can build and run locally
- [ ] Understands git workflow
- [ ] Completed first PR
- [ ] Knows team members
- [ ] Understands product basics
- [ ] Has access to all tools
### Week 2: Building
- [ ] Completed 3+ issues
- [ ] Participated in code review
- [ ] Understands architecture
- [ ] Attended key meetings
- [ ] Asked questions in Slack
### Week 3-4: Expanding
- [ ] Working on medium complexity issues
- [ ] Given code review feedback
- [ ] Understands deployment process
- [ ] Can debug common issues
- [ ] Pairing with team members
### Month 2: Growing
- [ ] Owns small feature
- [ ] Contributes to planning
- [ ] Reduced buddy check-ins
- [ ] Helping with documentation
### Month 3: Independent
- [ ] Owns features independently
- [ ] Participates fully in reviews
- [ ] Answers questions from others
- [ ] Potential buddy for next hire
### 90-Day Graduation
- [ ] Onboarding retro completed
- [ ] Full team member
- [ ] Clear on growth path
Buddy Program
Buddy Responsibilities
| Responsibility | Frequency | Duration |
|---|---|---|
| Daily check-in | Daily (Week 1-2) | 15 min |
| Code pairing | 2-3x per week | 1-2 hours |
| Answer questions | As needed | - |
| Weekly sync | Weekly (Month 1-3) | 30 min |
| Progress feedback | Bi-weekly | With manager |
Buddy Guidelines
## Buddy Guide
### DO
- Be available and approachable
- Proactively check in
- Share context and history
- Introduce to stakeholders
- Celebrate wins
- Give honest feedback
### DON'T
- Solve everything for them
- Let them struggle alone
- Skip check-ins
- Assume they'll ask
- Overwhelm with information
30/60/90 Day Goals
## 30/60/90 Plan: [Name]
### 30 Days: Learn
**Focus:** Understand product, team, codebase
| Goal | Success Criteria |
|------|------------------|
| Know the product | Can demo to someone |
| Navigate codebase | Can find relevant code |
| Complete tasks | 5+ issues closed |
| Build relationships | Met all team members |
### 60 Days: Contribute
**Focus:** Add value, increase ownership
| Goal | Success Criteria |
|------|------------------|
| Own features | Delivered 1 feature |
| Code quality | PRs need minimal revision |
| Process knowledge | Can work independently |
| Team participation | Active in discussions |
### 90 Days: Own
**Focus:** Full contributor, potential mentor
| Goal | Success Criteria |
|------|------------------|
| Feature ownership | Own area of codebase |
| Code review | Providing valuable feedback |
| Knowledge sharing | Documented something |
| Future focus | Clear on growth path |
Onboarding Feedback
Weekly Check-in Template
## Week [X] Check-in: [Name]
### How are you feeling?
[ ] Great [ ] Good [ ] Okay [ ] Struggling
### Wins this week
- [Win 1]
### Challenges
- [Challenge 1]
### Questions
- [Question 1]
### What would help?
- [Request 1]
### Feedback on onboarding
- [Feedback]
90-Day Retro
## Onboarding Retro: [Name]
### What went well?
- [Item 1]
### What could improve?
- [Item 1] → [Suggestion]
### What was missing?
- [Gap 1]
### Suggestions for next hire
- [Suggestion 1]
### How prepared do you feel?
[ ] Very [ ] Mostly [ ] Somewhat [ ] Not enough
Documentation for New Hires
## New Hire Guide
### Getting Started
1. [Setup guide link]
2. [Architecture overview link]
3. [Team processes link]
### Key Contacts
| Topic | Contact |
|-------|---------|
| Technical questions | [Buddy] |
| Process questions | [Manager] |
| IT issues | [IT Contact] |
| HR questions | [HR Contact] |
### Important Links
| Resource | Link |
|----------|------|
| Code repository | [Link] |
| Documentation | [Link] |
| Team wiki | [Link] |
| Project board | [Link] |
### Meeting Schedule
| Meeting | When | Purpose |
|---------|------|---------|
| Daily standup | [Time] | Sync |
| Sprint planning | [Time] | Planning |
| 1:1 with manager | [Time] | Support |
| Team retro | [Time] | Improvement |
### First Tasks
See issues labeled `good-first-issue` or `onboarding`
Metrics
| Metric | Target | How to Measure |
|---|---|---|
| Time to first PR | < 1 day | Git history |
| Time to first feature | < 4 weeks | Issue tracking |
| Onboarding satisfaction | > 4/5 | Survey |
| 90-day retention | 100% | HR data |
| Time to full productivity | < 3 months | Manager assessment |
Score
Total Score
70/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
✓LICENSE
ライセンスが設定されている
+10
✓説明文
100文字以上の説明がある
+10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
Reviews
💬
Reviews coming soon