felipecabargas
UserPM skills and workflow agents for Claude/Gemini — research to roadmap, sprint to stakeholder.
Categories
Indexed Skills (13)
build-user-persona
Build evidence-backed user personas from research inputs. Creates structured persona documents grounded in evidence, with each attribute clearly labeled as research-validated or inferred. Use this skill when you need personas for an FR, strategy doc, or design brief. Trigger on: "build a persona", "create user personas from this research", "who are our users", "describe our target user", "make a persona for [segment]", or when synthesised research is ready and needs a persona layer.
competitive-analysis
Structure a competitive landscape analysis — player profiles, capability comparison matrix, whitespace opportunities, and strategic implications. Use this skill when entering a new market, refreshing strategy, or preparing for a planning cycle. Trigger on: "do a competitive analysis", "who are our competitors", "compare us to X and Y", "what's the competitive landscape for [space]", "where is there whitespace in the market", "how do we stack up against [competitor]".
prioritize
Score and rank a list of features or initiatives using RICE by default. Scans existing strategy and OKRs to ground Impact scores in what the team is actually optimizing for. Use when deciding what to build next, preparing for planning, or presenting a ranked backlog to stakeholders. Accepts a pasted list, FR filenames, or a mix of both. Supports RICE (default), Agentic RICE (for AI-delegated work), ICE, and MoSCoW as alternative frameworks.
sprint-review
Generate a professional sprint review report for stakeholders — PMs, leadership, and cross-functional teams. Use this skill whenever a user wants to write up a sprint, summarize what the team shipped, produce a sprint retrospective document, recap what was completed in an iteration, or create a sprint summary for leadership. Triggers include: "write my sprint review", "generate a sprint recap", "create a sprint report", "summarize what we shipped this sprint", "help me write up our sprint for stakeholders", or any mention of sprint outcomes, velocity reports, or iteration summaries — even if they don't use the word "skill" or "report". Also trigger when a user pastes a list of tickets/tasks and asks for a write-up or summary.
synthesize-user-research
Synthesize raw user research (interview notes, survey results, support tickets, NPS verbatims) into structured insights: themes, pain points, jobs-to-be-done, and research gaps. Use this skill when you need to make sense of qualitative research data before writing a feature request or building personas. Trigger on: "synthesize my research", "what are the themes in these interviews", "extract insights from this feedback", "summarize what users are saying", "pull out the key themes from this data", or when someone pastes raw research notes.
verify-acceptance-criteria
Verify acceptance criteria quality and identify gaps. Use this skill whenever you need to evaluate acceptance criteria (ACs) to ensure they meet quality standards. Trigger on: "review these ACs", "check if these acceptance criteria are good", "validate my user story criteria", "improve our acceptance criteria", "audit these requirements", "do these ACs pass review", or similar requests. Also use proactively when someone shares acceptance criteria that look hastily written or vague. The skill analyzes criteria against five key dimensions (clarity, testability, outcome-focus, measurability, independence), scores issues by severity (critical/major/minor), and generates a structured report. It can also rewrite poor criteria into better ones or convert them to user story format.
write-feature-request
Guided Feature Request (FR) authoring. Assists the user in writing a high-quality FR by collecting structured inputs (problem, solution, outcomes, requirements), then auto-generates Acceptance Criteria for every requirement. If any AC cannot be written due to missing information, the skill identifies the gaps and prompts the user. Returns a polished FR in Markdown with nested ACs, open questions, and risks. Use this skill whenever a user needs to author or improve a feature request. Trigger on: "write a feature request", "help me write an FR", "create a feature spec", "draft a feature proposal", "I want to define a new feature", "turn this idea into a feature request", or similar requests.
write-okrs
Generate well-structured OKRs from a product strategy. Derives Objectives and Key Results from strategy pillars, challenges vague KRs, distinguishes outputs from outcomes, and links each OKR back to the strategy pillar it serves. Trigger on: "write our OKRs", "help me set OKRs for this quarter", "turn this strategy into OKRs", "what should our key results be", "draft Q[N] OKRs", or after completing write-product-strategy.
write-product-strategy
Generate comprehensive product strategy documents aligned with business goals. Use this when defining or updating your product's strategic direction, aligning teams on where to play and how to win, or creating a STRATEGY.md that bridges vision and execution. Triggers include: clarifying product strategy, articulating competitive positioning, defining strategic pillars, creating alignment documents, or answering 'what are we betting on as a company?' This skill scans existing project docs (roadmaps, market research, competitive analyses) to inform strategy, then either creates a new STRATEGY.md or updates an existing one.
write-release-notes
Convert sprint tickets and PRs into customer-facing release notes. Filters internal/infra work, rewrites ticket titles as user benefits, groups by category (New / Improved / Fixed), and adapts tone to the target channel. Trigger on: "write release notes", "turn these tickets into release notes", "what should we put in the changelog", "draft our release announcement", "write our changelog for [version]", or after a sprint-review session.
write-roadmap
Create a horizon-based product roadmap from strategy and OKRs. Organises work into Now/Next/Later themes derived from strategy pillars, marks items as committed vs. directional, and avoids fake precision (no hard dates unless explicitly provided). Trigger on: "write a roadmap", "create our ROADMAP.md", "help me plan the next few quarters", "what should we build and when", "turn this strategy into a roadmap", "build a Now/Next/Later plan", or after write-okrs.
write-stakeholder-update
Write a concise, data-led PM status update for leadership. Leads with a clear status signal (on track / at risk / blocked), surfaces concrete impact with numbers, shows OKR progress, flags decisions needed, and fits on one page. Trigger on: "write a stakeholder update", "draft my weekly PM update", "write a status update for leadership", "what should I tell leadership this week", "write my monthly PM report", or after a sprint-review session.
write-technical-brief
Write an engineering handoff document from a verified Feature Request. Covers scope boundaries, technical constraints, edge cases with recommended handling, open questions engineering needs answered, and integration points. Bridges PM spec and engineering without designing the solution. Trigger on: "write a technical brief", "help me hand this off to engineering", "what does eng need to know to build this", "create a technical handoff doc", "make this FR ready for the engineering team", or at the end of a feature request authoring session.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.