dpnmw/agents
1
0
Fork 0
mirror of https://github.com/wshobson/agents.git synced 2026-03-18 17:47:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

style: format all files with prettier

Browse Source
This commit is contained in:
Seth Hobson
2026-01-19 17:07:03 -05:00
parent 8d37048deb
commit 56848874a2
355 changed files with 15215 additions and 10241 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
plugins/git-pr-workflows/commands/onboard.md
View File

@@ -12,6 +12,7 @@ You are given the following context:
$ARGUMENTS
Parse the arguments to understand:
- **Role details**: Position title, level, team, reporting structure
- **Start date**: When the new hire begins
- **Location**: Remote, hybrid, or on-site specifics
@@ -96,6 +97,7 @@ Systematic introduction to technical landscape:
Complete configuration for productive development:
1. **Local Environment**
```
- IDE/Editor setup (VSCode, IntelliJ, Vim)
- Extensions and plugins installation
@@ -223,6 +225,7 @@ Ensuring onboarding effectiveness and iteration:
### Software Engineer Onboarding (30/60/90 Day Plan)
**Pre-Start (1 week before)**
- [ ] Laptop shipped with tracking confirmation
- [ ] Accounts created: GitHub, Slack, Jira, AWS
- [ ] Welcome email with Day 1 agenda sent
@@ -230,6 +233,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Manager prep: role doc, first tasks identified
**Day 1-7: Foundation**
- [ ] IT setup and security training (Day 1)
- [ ] Team introductions and role overview (Day 1)
- [ ] Development environment setup (Day 2-3)
@@ -238,6 +242,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Daily buddy check-ins (15 min)
**Week 2-4: Immersion**
- [ ] Complete 5+ PR reviews as observer
- [ ] Shadow senior engineer for 1 full day
- [ ] Attend all team ceremonies
@@ -246,6 +251,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Set up local development for all services
**Day 30 Checkpoint:**
- 10+ commits merged
- All onboarding modules complete
- Team relationships established
@@ -253,6 +259,7 @@ Ensuring onboarding effectiveness and iteration:
- First bug fix deployed to production
**Day 31-60: Contribution**
- [ ] Own first small feature (2-3 day effort)
- [ ] Participate in technical design review
- [ ] Shadow on-call engineer for 1 shift
@@ -261,6 +268,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Contribute to team documentation
**Day 60 Checkpoint:**
- First feature shipped to production
- Active in code reviews (giving feedback)
- On-call ready (shadowing complete)
@@ -268,6 +276,7 @@ Ensuring onboarding effectiveness and iteration:
- Cross-team relationships building
**Day 61-90: Integration**
- [ ] Lead a small project independently
- [ ] Participate in planning and estimation
- [ ] Handle on-call issues with supervision
@@ -276,6 +285,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Build relationship with product/design
**Day 90 Final Review:**
- Fully autonomous on team tasks
- Actively contributing to team culture
- On-call rotation ready
@@ -285,6 +295,7 @@ Ensuring onboarding effectiveness and iteration:
### Remote Employee Onboarding (Distributed Team)
**Week 0: Pre-Boarding**
- [ ] Home office stipend processed ($1,500)
- [ ] Equipment ordered: laptop, monitor, desk accessories
- [ ] Welcome package sent: swag, notebook, coffee
@@ -292,6 +303,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Time zone preferences documented
**Week 1: Virtual Integration**
- [ ] Day 1: Virtual welcome breakfast with team
- [ ] Timezone-friendly meeting schedule created
- [ ] Slack presence hours established
@@ -300,6 +312,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Daily "coffee chats" with different team members
**Week 2-4: Remote Collaboration**
- [ ] Pair programming sessions across timezones
- [ ] Async code review participation
- [ ] Documentation of working hours and availability
@@ -308,6 +321,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Contribution to team wiki and runbooks
**Ongoing Remote Success:**
- Weekly 1:1 video calls with manager
- Monthly virtual team social events
- Quarterly in-person team gathering (if possible)
@@ -318,6 +332,7 @@ Ensuring onboarding effectiveness and iteration:
### Senior/Lead Engineer Onboarding (Accelerated)
**Week 1: Rapid Immersion**
- [ ] Day 1: Leadership team introductions
- [ ] Day 2: Full system architecture deep-dive
- [ ] Day 3: Current challenges and priorities briefing
@@ -326,6 +341,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] End of week: Initial observations documented
**Week 2-3: Assessment and Planning**
- [ ] Review last quarter's postmortems
- [ ] Analyze technical debt backlog
- [ ] Audit current team processes
@@ -334,6 +350,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Propose initial technical improvements
**Week 4: Taking Ownership**
- [ ] Lead first team ceremony (retro or planning)
- [ ] Own critical technical decision
- [ ] Establish 1:1 cadence with team members
@@ -342,6 +359,7 @@ Ensuring onboarding effectiveness and iteration:
- [ ] Submit first major architectural proposal
**30-Day Deliverables:**
- Technical assessment document
- Team process improvement plan
- Relationship map established
@@ -353,6 +371,7 @@ Ensuring onboarding effectiveness and iteration:
### Complete Day 1 Checklist
**Morning (9:00 AM - 12:00 PM)**
```checklist
- [ ] Manager welcome and agenda review (30 min)
- [ ] HR benefits and paperwork (45 min)
@@ -363,6 +382,7 @@ Ensuring onboarding effectiveness and iteration:
```
**Afternoon (1:00 PM - 5:00 PM)**
```checklist
- [ ] Lunch with buddy and team (60 min)
- [ ] Laptop setup with IT support (90 min)
@@ -374,13 +394,13 @@ Ensuring onboarding effectiveness and iteration:
### Buddy Responsibility Matrix
| Week | Frequency | Activities | Time Commitment |
|------|-----------|------------|----------------|
| 1 | Daily | Morning check-in, pair programming, question answering | 2 hours/day |
| 2-3 | 3x/week | Code review together, architecture discussions, social lunch | 1 hour/day |
| 4 | 2x/week | Project collaboration, introduction facilitation | 30 min/day |
| 5-8 | Weekly | Progress check-in, career development chat | 1 hour/week |
| 9-12 | Bi-weekly | Mentorship transition, success celebration | 30 min/week |
| Week | Frequency | Activities | Time Commitment |
| ---- | --------- | ------------------------------------------------------------ | --------------- |
| 1 | Daily | Morning check-in, pair programming, question answering | 2 hours/day |
| 2-3 | 3x/week | Code review together, architecture discussions, social lunch | 1 hour/day |
| 4 | 2x/week | Project collaboration, introduction facilitation | 30 min/day |
| 5-8 | Weekly | Progress check-in, career development chat | 1 hour/week |
| 9-12 | Bi-weekly | Mentorship transition, success celebration | 30 min/week |
## Execution Guidelines
@@ -391,4 +411,4 @@ Ensuring onboarding effectiveness and iteration:
5. **Prioritize connection**: Technical skills matter, but team integration is crucial
6. **Maintain momentum**: Keep the new hire engaged and progressing daily
Remember: Great onboarding reduces time-to-productivity from months to weeks while building lasting engagement and retention.
Remember: Great onboarding reduces time-to-productivity from months to weeks while building lasting engagement and retention.