From people-management
Prepares 1:1 meeting prep sheets for direct reports by surfacing recent work, wins, friction, wellbeing signals, and goal progress from Slack, Drive, Notion, anchored in performance framework.
npx claudepluginhub techwolf-ai/ai-first-toolkitThis skill uses the workspace's default tool permissions.
> **Great 1:1s live at the intersection of performance and care.** Development keeps growth alive. Wellbeing makes sure the person behind the work is seen. Both matter every time.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Great 1:1s live at the intersection of performance and care. Development keeps growth alive. Wellbeing makes sure the person behind the work is seen. Both matter every time.
Deep-dive preparation for 1:1 meetings with a specific direct report, anchored in the org's performance framework (from manager-context/performance-framework.md) and organizational values.
If any MCP connector is unavailable, follow the connector unavailability protocol in ../../references/operating-principles.md.
If a name is provided, match it against manager-context/team/ profiles.
If no name is specified, check the calendar for the next upcoming 1:1 meeting and identify the attendee.
If ambiguous:
Which team member? Your upcoming 1:1s are:
- [Name] -- [day] at [time]
- [Name] -- [day] at [time]
Load the team member's profile from manager-context/team/[name].md for:
If no profile exists:
โ ๏ธ No profile found for [name]. Run /setup to build team context, or I'll work with what I can find from sources directly.
Slack (last 7-14 days):
Google Drive:
Notion:
Compile into a "recent activity" summary.
Look for signals (NOT diagnoses -- signals for the manager to explore):
Slack:
Calendar:
Important: Frame these as conversation starters, not assessments:
๐ก Potential topics to explore (signals, not conclusions):
- [Name] asked about [topic] in #channel 3 times this week without a clear resolution -- might be a blocker worth discussing
- [Name]'s activity in #project-channel has been lower than usual -- could be fine, but worth checking in
Scan for signals related to the organization's values (from manager-context/values.md) -- these give the manager conversation threads beyond just goals and deliverables.
If no values are configured, focus on these universal management dimensions:
Wellbeing & Energy:
Team Connection & Collaboration:
Communication & Transparency:
Resourcefulness & Problem-Solving:
Ownership & Initiative:
If organizational values are configured, map these dimensions to the specific values and use value names in the output.
Compile into a brief values snapshot (not a scorecard -- conversation prompts):
Values Snapshot:
- [Value/Dimension 1]: [observation or "no signal"]
- [Value/Dimension 2]: [observation or "no signal"]
...
Only include values/dimensions where there's a meaningful signal -- don't force all of them every time.
Using the goals location from the team member's profile:
Notion:
Google Drive:
Reference the org's performance framework dimensions (from manager-context/performance-framework.md). Use the org's dimension names and sub-dimensions when checking goal progress. If this file doesn't exist, ask the manager to run /setup first.
See the "Evidence Gathering Guidelines" section in ../../references/performance-framework.md for what to look for per dimension type:
๐ Development Goal Status:
- Goal 1: "[goal text]" -- [status: on track / needs attention / no update since [date]]
- Goal 2: "[goal text]" -- [status]
- Development area: "[area]" -- [any evidence of progress or attention]
โฐ Last goal update: [date] -- [flag if >6 weeks old]
Search for the last 1:1 document/notes:
Google Drive: Search "[name] 1:1", "one on one [name]"
Extract:
๐ From last 1:1 ([date]):
Open items:
- [ ] [Manager] to [action] -- [status: done/pending/unknown]
- [ ] [Team member] to [action] -- [status: done/pending/unknown]
Parked topics: [if any]
Read references/output-template.md for the full output template structure.
Spawn a sub-agent to review the prep sheet with fresh eyes. The reviewer should:
Incorporate the reviewer's feedback before presenting the final prep sheet.
Here's your prep for your 1:1 with [name]. Anything you'd like me to dig deeper on?
Read ../../references/operating-principles.md for shared operating principles (data scope, DM flagging, signals vs diagnoses, connector unavailability).
Additional notes specific to this skill: