Agent
Use when evaluating third-party AI tools, models, APIs, or platforms before purchase. Trigger for vendor selection, build-vs-buy decisions with external options, model-provider comparisons, or when the user needs a structured evaluation framework for procurement. Distinct from the-reducer (build-vs-buy internal…
Skill Claude CodeCodex
Use when scoping AI features, deciding build-vs-buy-vs-rule, designing eval harnesses, choosing models for cost/latency trade-offs, or planning guardrails for LLM-based products. Trigger when the user is doing AI product management work — feasibility, architecture, or reliability decisions for probabilistic systems.
Skill Claude CodeCodex
Use to log something from the current conversation into the user's bettersense memory without re-typing it — a decision that just got made, a win that surfaced mid-discussion, an observation about a stakeholder, a self-insight. Trigger phrases include "log this", "capture this", "save that decision", "add that to my…
Skill Claude CodeCodex
Use for a periodic (quarterly / annual) career retrospective across the ENTIRE bettersense memory — producing a longitudinal self-assessment with cited growth deltas since the last retro and the honest gaps to work on next. Trigger phrases include "run my career retro", "where am I in my career", "annual…
Skill Claude CodeCodex
Use when the user wants to coach someone — a report, peer, or mentee — through a problem rather than solve it for them. Trigger phrases include "coach me through how to talk to [report]", "I want to help [name] figure out X without telling them what to do", "let me practice a coaching conversation", "GROW conversation…
Skill Claude CodeCodex
Use to track what the user has promised — to their manager, execs, partner teams — and to keep those promises from silently going stale. Trigger phrases include "what have I committed to", "add a commitment", "I promised X by Friday", "am I overcommitted", "help me say no to this", "I need to renegotiate a deadline".…
Skill Claude CodeCodex
Use when the user makes or revisits a meaningful product, technical, or organizational decision and wants it captured in a durable, ADR-style format. Trigger when they say "we decided to…", "let's go with X over Y", "I need to write up the call we made on…", or when reviewing a past decision they can't fully…
Skill Claude CodeCodex
Use when the user is preparing for a demo — exec review, customer pitch, board update, investor meeting, sales call, or all-hands. Trigger phrases include "I'm demoing X tomorrow", "help me prep for the review", "what could go wrong in this demo?". Especially valuable for AI-feature demos, where probabilistic systems…
Skill Claude CodeCodex
Use to health-check the user's bettersense memory directory — validate the file layout, catch problems before they cost data, and set up backups. Trigger phrases include "run bettersense doctor", "check my reflection files", "is my bettersense data okay", "something seems off with my stakeholder files", "back up my…
Skill Claude CodeCodex
Use when an EM wants to assess how well their engineering systems and processes are working — not team morale or people dynamics (that's team-diagnosis), but the productivity layer: are the right things being measured, where is developer experience breaking down, is onboarding a signal of deeper friction, and how to…
Skill Claude CodeCodex
Use when the user needs a decision or backing from executives and is preparing the meeting or memo that gets it — QBRs, roadmap reviews, headcount asks, architecture investment pitches, "I'm presenting to the VP/C-suite next week". Trigger phrases include "prep my exec readout", "I'm presenting to leadership", "I need…
Skill Claude CodeCodex
Use when the user is preparing to give feedback to a teammate, direct report, peer, or stakeholder — performance reviews, 1:1 prep, post-incident conversations, peer reviews, 360s, written async feedback, or any moment they're drafting "how do I tell them that…". Apply the COIN structure to compose the message and the…
Skill Claude CodeCodex
Use when the user wants to systematically identify, categorize, and quantify "glue work" (non-core technical activities like onboarding, documentation, unblocking, cross-team alignment, process improvement) on themselves or their team. Trigger phrases include "what glue work am I doing", "audit my glue work", "what…
Skill Claude CodeCodex
Use when designing interview loops, writing interview questions or rubrics, calibrating panel feedback, running hiring debriefs, or making a hire/no-hire call. Trigger phrases include "design an interview loop for [role]", "write interview questions for [signal]", "help me run the debrief", "should we hire X", "I need…
Skill Claude CodeCodex
Use when a PM or team wants to stress-test whether their work is actually connected to something the business cares about. Runs before strategy-doc or prioritization-frameworks — it answers "are we even pointed at the right thing?" Trigger phrases include "are we doing the right work?", "I'm worried my team isn't…
Skill Claude CodeCodex
Use when the user needs to move a person, team, or decision without having direct authority over them — driving an architecture change across teams, getting buy-in from a skeptical principal engineer, persuading an exec sponsor, mobilizing a coalition for a contentious initiative, or pushing back on a leader's…
Skill Claude CodeCodex
Use when the user is navigating people/leadership situations as a PM — managing up to executives, managing down to a team, cross-functional conflict, 1:1s, performance reviews, post-mortems, incident response, roadmap negotiation, or stakeholder communication. Trigger when the question is about how to handle a person…
Skill Claude CodeCodex
Use when managing engineers who naturally gravitate toward glue work (onboarding, documentation, unblocking, process improvement) and need protection from burnout, visibility for their impact, and career development that doesn't force them off the IC track. Trigger phrases include "my report does too much glue", "how…
Skill Claude CodeCodex
Use when the user is designing the metric tree for a feature (especially an AI feature) — picking a north star, leading and lagging indicators, quality metrics, and counter-metrics. Trigger phrases include "what should we measure for…", "how do we know if this is working?", "I need to define success for…", or any spec…
Skill Claude CodeCodex
Use when a new model version ships (or a current one is deprecated) and the user must decide whether and how to migrate a LIVE AI feature — "Claude X just came out, should we move?", "our model is being deprecated in 90 days", "the new model is cheaper, can we switch?", "plan the migration to [model]". Runs the…
Skill Claude CodeCodex
Use when the user is preparing for a 1:1 — as a manager preparing to meet with a report, as an IC preparing to meet with their manager, or as a peer preparing for a regular sync. Trigger phrases include "I have a 1:1 with X tomorrow", "help me prep for my 1:1", "what should I bring up in my next 1:1?". Builds an…
Skill Claude CodeCodex
Use to surface unsolicited patterns the user hasn't explicitly asked about — across stakeholder reflections, wins log, self-reflect entries, and (eventually) pulse reports. Trigger phrases include "what patterns am I missing", "anything notable across my files", "scan my reflections for things I should know", "weekly…
Skill Claude CodeCodex
Use when the user is dealing with underperformance, considering a PIP, navigating a brilliant-jerk pattern, documenting concerns, or preparing for a hard performance conversation. Trigger phrases include "I have a report who's underperforming", "should I PIP X", "I need to document this", "how do I have the hard…
Skill Claude CodeCodex
Use for pre-mortem analysis of decisions, projects, or initiatives — solo and lightweight, or facilitated with a team before a launch or strategic commitment. Trigger when the user says "what could go wrong", "risk assessment", "pre-mortem this", "let's run a pre-mortem", or when evaluating risks for a plan. Applies a…