All authors
Claude Skills by Sidsaladi9
github.com/Sidsaladi962 skills6 installs138 views
- Write SpecTurns a vague feature idea or problem statement into a structured, review-ready feature spec or PRD with goals, non-goals, success metrics, and testable acceptance criteria. Use when a PM says "write a PRD", "spec this feature", "turn this idea into a spec", "scope this", "define success metrics", "write acceptance criteria", or needs to break a big ask into a phased spec.Votes: 0GitHub stars: 5
- Assumption TestSurfaces the hidden assumptions an idea depends on, sorts them by risk (likelihood-it's-false × damage-if-false) across desirability, viability, feasibility, and usability, then designs the cheapest test for the riskiest ones. Use when you say "what has to be true for this to work," "what's the riskiest assumption," "should we validate before building," "how do we de-risk this bet," or "this idea feels shaky and I can't say why."Votes: 0GitHub stars: 5
- Competitive BriefUse when you need a competitive analysis brief or competitor teardown for one or more rivals or a feature area. Triggers include "competitive analysis", "build a battlecard for [competitor]", "how do we compare to X", "where should we differentiate", "competitor teardown", and prepping board or sales materials on the competitive landscape.Votes: 0GitHub stars: 5
- Feedback AnalysisTurns a large volume of customer feedback (support tickets, app-store reviews, NPS verbatims, survey free-text) into ranked themes with sentiment, volume, and trend-over-time. Use when you have hundreds or thousands of comments and need to know "what are people complaining about," "what changed since last quarter," or "which theme should we fix first." The quant/at-scale complement to interview-depth synthesis.Votes: 0GitHub stars: 5
- Market AnalysisRuns a structured environmental scan using SWOT, PESTEL, Porter's Five Forces, and Ansoff growth options, then synthesizes them into 2-3 strategic implications. Use when you need to assess a market before entering it, pressure-test a strategy, prep a board or planning deck, answer "what are the forces shaping this market" or "where should we grow," or turn scattered market notes into a decision.Votes: 0GitHub stars: 5
- Pre MortemRuns a Klein pre-mortem on a project — assumes it already failed, brainstorms why, scores each failure mode by likelihood × impact, and attaches a mitigation plus an early-warning signal to the top risks. Use when launching a feature, kicking off a quarter, or before a big bet and you want to ask "imagine this shipped and flopped — what killed it?" or "where is this most likely to go wrong?"Votes: 0GitHub stars: 5
- Red TeamAdversarially attacks a PRD, strategy, or plan to find its holes before reality does — naming load-bearing assumptions, weakest links, and what a skeptical exec or competitor would exploit. Steelmans the plan first, then attacks it hard. Use when you're about to ship a doc to leadership, "this feels too clean," "what am I missing," "poke holes in this," "what would kill this," or prepping for a tough review.Votes: 0GitHub stars: 5
- Synthesize ResearchSynthesize user research from interviews, surveys, and feedback into structured, evidence-backed insights. Use when you have a pile of notes to make sense of and say things like "synthesize these interviews", "find themes in this feedback", "what are users telling us", "turn this research into insights", or "analyze these support tickets". Extracts themes ranked by frequency and impact, then translates them into roadmap recommendations.Votes: 0GitHub stars: 5
- Triage RequestsSorts a pile of inbound feature requests from sales, support, and users into themes, quantifies demand behind each, and recommends build / watch / decline with a templated reply for every requester. Use when you say "I have 40 requests to go through," "what are people actually asking for," "triage this feedback dump," "theme these tickets," or "should we build this or say no?"Votes: 0GitHub stars: 5
- Value PropositionMaps what customers actually want against what your product relieves and creates, using the Value Proposition Canvas, and produces the fit assessment plus the statements that come out of it. Use when a PM says "what's our value prop", "map the value proposition", "why do customers care", "our messaging isn't landing", or when the product does many things and nobody can say which one is the reason people buy.Votes: 0GitHub stars: 5
- Win LossRuns a win/loss analysis across decided deals to find why you actually win and lose, separating stated reasons from real causes. Use when a PM or PMM says "why are we losing deals", "run a win-loss", "analyze these lost deals", "what's killing our close rate", "sales says it's price", or when the same objection keeps surfacing and nobody has checked it against the data.Votes: 0GitHub stars: 5
- SegmentationSegment a market or user base by needs and behavior — not just demographics — then size, score, and pick a beachhead segment with a defensible rationale. Use when someone says "segment this market", "who should we target first", "find our beachhead", "break our users into segments", "which customers do we prioritize", or "TAM/SAM by segment".Votes: 0GitHub stars: 5