careerpacer-1on1-and-idp
VerifiedTurn freeform 1:1 meeting notes into a structured CareerPacer OneOnOne file under data/1on1/, and create or update IDPAction entries in the current year's data/idp/<year>.md, linked back to that 1:1. Use this skill when the user dictates or pastes notes from a 1:1 that just happened or is upcoming, or asks to "log a 1:1", "write up this meeting", "prep for my next 1:1", "add/update an IDP action", or "link this to my growth plan".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| examples/data/1on1/2026-01-19.md | markdown | 1.1 KB |
| examples/data/1on1/2026-02-16.md | markdown | 1.0 KB |
| examples/data/1on1/2026-03-16.md | markdown | 989 B |
| examples/data/1on1/2026-04-20.md | markdown | 985 B |
| examples/data/1on1/2026-05-18.md | markdown | 1.0 KB |
| examples/data/1on1/2026-06-15.md | markdown | 1.1 KB |
| examples/data/1on1/2026-07-13.md | markdown | 1.1 KB |
| examples/data/evaluation/2026-annual.md | markdown | 2.4 KB |
| examples/data/idp/2026.md | markdown | 2.8 KB |
| examples/data/profile.json | config | 139 B |
| scripts/generate_index.py | script | 1.3 KB |
| scripts/validate_data.py | script | 5.7 KB |
examples/data/idp/2026.md
View on GitHub---
year: 2026
actions:
- id: idp-2026-001
title: Ship and monitor a production ML model end-to-end (move beyond notebook experiments)
status: in_progress
start_date: 2026-06-15
target_date: 2026-12-18
source: 1on1-2026-06-15
linked_evidence:
- "[2026-04-20] Proposed the workout-streak recommendation model as a candidate to take beyond the notebook stage; agreed to include a deployment/monitoring plan"
- "[2026-05-18] Shipped v1 behind a feature flag; monitoring not yet in place"
- "[2026-06-15] Growth area formalized in annual review — next concrete step is defining monitoring/alerting thresholds"
- "[2026-07-13] Monitoring dashboard live with alert thresholds configured; manager confirmed this closes the gap flagged in June"
- id: idp-2026-002
title: Build consistent visibility and assertiveness in cross-team/leadership meetings (second-language, remote context)
status: in_progress
start_date: 2026-06-15
target_date: 2026-11-30
source: 1on1-2026-06-15
linked_evidence:
- "[2026-02-16] Manager flagged staying quiet in cross-team roadmap sync despite having relevant input; agreed to prep 2-3 points ahead of live meetings"
- "[2026-03-16] Spoke up once in leadership sync, got cut off, didn't try again same call"
- "[2026-04-20] Spoke up unprompted in a smaller cross-team meeting with a concrete latency number"
- "[2026-05-18] Spoke up in the full leadership sync, unprompted, no advance script needed"
- "[2026-06-15] Growth area formalized in annual review — goal is consistency, not just occasional instances"
- "[2026-07-13] Spoke up unprompted in leadership sync with a specific adoption-rate number; starting to feel routine rather than forced"
- id: idp-2026-003
title: Own a project end-to-end, from scoping through stakeholder-facing delivery
status: in_progress
start_date: 2026-06-15
target_date: 2026-12-18
source: 1on1-2026-06-15
linked_evidence:
- "[2026-03-16] Manager raised the idea of owning one project fully rather than contributing pieces to others'; agreed to bring a proposal"
- "[2026-04-20] Selected the workout-streak recommendation model as the end-to-end ownership project"
- "[2026-06-15] Growth area formalized in annual review — goal expanded to include a full stakeholder-facing delivery, not just an internal deploy"
- "[2026-07-13] Led the first stakeholder-facing demo end-to-end, answering questions without manager stepping in"
---
Notes: all three actions were formalized on the same day (2026-06-15) as a
direct follow-up to my first annual review, but the underlying themes
were visible in 1:1s for months beforehand — evidence entries before that
date capture that earlier, informal context.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |