1:1 Prep
Walk into every one-on-one with a clean agenda, your wins documented, and the asks you need to make. Never waste a 1:1 again.
Overview
The Sapling IC 1:1 Prep skill turns a software engineer's real work into a ready-to-use prep document for their next one-on-one. It reads the tools an engineer already works in, then assembles a personalized brag doc, blocker list, and growth view, so they walk into the meeting already knowing what they shipped, what they want credit for, and where they need help. The document opens with a hard metrics section that puts specific numbers in team context, giving the engineer and their manager the same signals to look at.
Inputs
- Pulls from your connected work tools — GitHub/GitLab, JIRA/Linear, calendar, chat, email, docs, incidents, and goals/HR.
- Gathers your goals, org structure, and active projects through quick prompts.
- Asks what you want to cover in the meeting — answer or skip.
Outputs
- A self-contained HTML dashboard with hard metrics in team context, an AI summary, wins, and blockers/asks.
- Recurring trends, a feedback section, and a goals-and-growth view mapped to promotion criteria.
- Standout items starred, with every ticket, PR, meeting, and doc linked back to its source.
Why it matters
Engineers spend minutes reviewing and trimming rather than hours reconstructing what they did from memory. Because every metric and claim traces back to real pulled data, the document reflects actual work rather than guesswork, and accomplishments that tend to slip a manager's notice get surfaced explicitly. The growth view connects current work to what the next level expects, making promotion conversations concrete. The engineer owns the document and decides what to share, and the skill reads tools only, never sending, posting, or changing anything.
Example
An engineer has a one-on-one tomorrow and types “help me prep for my 1:1.” The skill shows which of their tools are connected, then scopes the period to the weeks since their last 1:1, detected from a recurring calendar event. It pulls their merged pull requests, closed tickets, review activity, and chat threads, and previews the highlights as a short list for the engineer to confirm. They add their goal of growing in system design and name their two active projects. The finished document shows their completion rate against the team, flags one pull request that has been waiting on review past the team norm with a concrete next step, surfaces a cross-team fix that helped another squad and was off their manager's radar, and lists three people to ask for feedback ahead of an upcoming demo.