Skip to content

karlvmsousa/CareerPacer

careerpacer-1on1-and-idp

Verified

Turn 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".

examples/data/1on1/2026-06-15.md

View on GitHub
---
id: 1on1-2026-06-15
date: 2026-06-15
status: logged
attendees:
  - John Ferreira
  - Alex Turner
follow_ups:
  - Define concrete monitoring/alerting thresholds for the workout-streak model before end of Q3
linked_actions:
  - idp-2026-001
  - idp-2026-002
  - idp-2026-003
tags:
  - review-followup
---

Follow-up after my first annual review (360-degree). Alex walked through
the three growth areas that came out of it, and we're turning them into
IDP actions:

1. Move from notebook experiments to shipped, monitored production ML —
   the workout-streak model is a good start but needs real monitoring.
2. Keep building visibility/assertiveness in cross-team and leadership
   meetings — I've made clear progress already; the goal now is for it
   to be consistent rather than occasional.
3. Own a project end-to-end — the workout-streak model counts, but Alex
   wants to see it through to a full stakeholder-facing delivery, not
   just an internal deploy.

The review feedback matched what I expected from these last few months
of 1:1s, which I appreciated — no surprises. Agreed to treat all three
as active IDP actions starting today.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall