one-on-one-prep
Prepare for a 1:1 so it drives outcomes instead of becoming a status update. Use when asked to prep for a one-on-one, build a 1:1 agenda, prepare to talk to your manager (or a report), or raise something hard in a 1:1. Produces a focused 1:1 agenda — your top topics with the outcome you want for each, the asks, updates kept brief, and growth/feedback threads, tuned to direction (with your manager vs. with a report).
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/one-on-one-prep && cp -r /tmp/one-on-one-prep/plugins/pm-career/skills/one-on-one-prep ~/.claude/skills/one-on-one-prepSKILL.md
# One-on-One Prep Skill The 1:1 is the highest-leverage meeting you have — and it's wasted when it defaults to status (which belongs in writing). This skill preps an agenda built around the **outcomes you want**: the decisions to unblock, the asks to make, the feedback to exchange, and the career threads to keep warm — so 30 minutes moves things instead of just reporting them. ## Required Inputs Ask for these only if they aren't already provided: - **Direction** — prepping for a 1:1 **with your manager** (managing up) or **with your report** (managing down)? The agenda differs. - **What's on your mind** — blockers, decisions, tensions, wins, career topics (rough notes are fine). - **Anything time-sensitive** or any hard thing you've been avoiding raising. - **Last 1:1's follow-ups**, if any. ## Output Format ### 1:1 Prep — with [name], [date] **1. Top topics (most important first)** — for each: the topic, **the outcome you want**, and the framing. Lead with what needs a decision or unblock, not updates. | Topic | Outcome I want | How I'll frame it | |---|---|---| **2. Asks** — explicit requests (a decision, air cover, a connection, time). Naming the ask is the point of the meeting. **3. Status — kept brief** — 2–3 bullets of what they genuinely need to know; link the rest. Don't let this eat the meeting. **4. Feedback (both ways)** — feedback to give (specific, kind, actionable) and a prompt to ask for feedback on yourself. **5. Growth / career** — the longer-game thread to keep warm (a stretch goal, a development area, a promotion track). **6. Follow-ups** — from last time, and what you'll commit to from this one. *Direction note:* **managing up** → lead with decisions you need and asks; surface risks early; make it easy to help you. **Managing down** → lead with their agenda and growth, listen more than you talk, end with clear next steps. ## Quality Checks - [ ] Topics lead with a desired **outcome**, not a status recap - [ ] At least one explicit **ask** is named - [ ] Status is condensed to a few bullets (the rest written/linked) - [ ] Feedback flows both ways, and is specific and actionable - [ ] A growth/career thread is kept on the agenda, not just the urgent stuff - [ ] The agenda is tuned to direction (managing up vs. down) ## Anti-Patterns - [ ] Do not turn the 1:1 into a status report — status belongs in writing; use the live time for decisions, feedback, and growth - [ ] Do not avoid the hard topic — name it, framed constructively; the 1:1 is the safest place to raise it - [ ] Do not arrive without an ask — "anything you need?" wastes the leverage - [ ] Do not let career/growth fall off when things are busy — it's the first thing dropped and the most costly - [ ] Do not over-pack — 3 real topics beat 10 skimmed ## Based On 1:1 management practice (Andy Grove, *High Output Management*; manager-tools 1:1 cadence) — outcome-led agendas, managing up and down.
Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.