saurabhships
UserA growing library of reusable PM skills and frameworks for turning product management judgment into repeatable, shareable playbooks.
Categories
Indexed Skills (8)
call-insight-extraction
Extract structured, tagged insights from a customer call transcript — pain points, feature asks, objections, buying signals, and action items — ready to route to a backlog or share with a team. Use whenever a call transcript, meeting recording, or customer conversation needs to become a shareable summary rather than sit as raw notes, especially for sales calls, customer success check-ins, user research interviews, or support escalations.
feedback-triage-scoring
Score and rank a batch of customer feedback (feature requests, complaints, bugs) into a single prioritized list using a blended ARR-exposure, frequency, and RICE framework. Use whenever feedback from multiple sources — support tickets, sales notes, call insights, reviews, community posts — needs to be turned into one ranked list rather than assessed item by item, or when someone asks "what should we actually prioritize" from a pile of scattered feedback.
business-requirements-document
Draft a Business Requirements Document (BRD) that captures the business problem, measurable objectives, scope, stakeholders, and success criteria for an initiative, before any solution is defined. Use when a leadership team, business sponsor, or cross-functional stakeholder group needs alignment on why an initiative should happen and what business outcome it's meant to produce — typically the step before a PRD gets written.
competitive-intelligence-briefing
Turn scattered competitor signals — changelogs, pricing pages, reviews, sales win/loss notes, hiring signals, funding news — into a structured brief that says what changed, why it matters, and whether it needs a response. Use for a recurring competitive scan (e.g., a weekly Monday-morning brief) or whenever a specific competitor move needs to be assessed on the spot.
internal-signal-scouting
Surface and tag product ideas, escalations, and competitive intel that surface in internal channels (Slack, Teams) from sales, support, and customer success — before they get lost in scroll. Use for a scheduled sweep of designated internal channels, or when compiling a weekly internal-pulse digest. Not for monitoring channels that haven't been explicitly designated for this purpose.
market-industry-insights-briefing
Turn broader market and industry signals — analyst reports, regulatory shifts, macro trends, adjacent-market moves, category-wide funding patterns — into a structured brief connecting external change to strategic implications, distinct from any single named competitor's actions. Use for a recurring cadence or ahead of planning cycles when leadership needs "what's happening in our market" synthesized rather than gathered raw.
product-requirements-document
Draft a Product Requirements Document (PRD) that translates an established business need into a buildable spec — user stories, functional and non-functional requirements, scope, and testable acceptance criteria — for engineering, design, and QA. Use once a business case exists (via a BRD or other evidence) and it's time to define exactly what gets built.
usage-trend-narration
Turn raw usage numbers (WAU, MAU, feature adoption, retention) into an honest, confidence-qualified narrative — the "why" behind the number, not just the number itself. Use whenever a weekly or monthly usage report needs to go from a chart into a written update, or whenever someone asks "why did this metric move."
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.