setup-context
The `/setup-context` command creates or updates a `pm-context.md` file that stores essential product and audience information for a skill library. It interviews the user to gather details about company, product stage, target audience, voice preferences, key metrics, competitors, and constraints, then generates a concise reference document. Subsequent skill executions read this file first to deliver outputs tailored to the user's specific context rather than generic templates.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/HEAD/commands/setup-context.md -o ~/.claude/commands/setup-context.mdsetup-context.md
Set up the user's **Skill Memory** (`pm-context.md`). 1. If `pm-context.md` already exists at the project root, read it and offer to update it. Otherwise, base the structure on `templates/pm-context.example.md`. 2. Interview the user briefly to fill it in — ask only for what's missing, a few at a time, using any seed notes here: $ARGUMENTS. Cover: company/product, stage, primary audience, voice/tone & formatting defaults, the metrics that matter, key competitors + differentiator, and any hard constraints. 3. Write a concise, concrete `pm-context.md` (no filler). Keep each section to a few lines. 4. Confirm it's saved and explain the payoff: from now on, when running any skill or workflow recipe, **read `pm-context.md` first and apply it** — match the user's product, audience, and voice — so the first draft is tailored, not generic. Going forward, treat `pm-context.md` (if present) as standing context for every skill in this library.
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.