Product Skills
Skills for founders and product people — PRDs, scope cuts, interview synthesis, competitor teardowns — that run on claude.ai, Claude Code, and Cowork.
Competitor Teardown
Build a structured teardown of one competitor from the pages, screenshots, and pricing text you paste in: positioning, target customer, pricing model, a feature table with evidence, and the wedge opportunities where you could win, with every unknown flagged as something to research rather than guessed. Use when sizing up a competitor before a PRD, a pitch, or a pricing decision and you want an analysis grounded only in what they publish.
Investor Update Writer
Draft a monthly investor update from the metrics and notes you paste: a three-line TL;DR, a metrics table with month-over-month deltas computed only from the numbers you supplied, wins, misses stated with their numbers, explicit asks, and a runway note. Never fills in a figure you did not give. Use when the update is due, the raw numbers are in a spreadsheet export or a scratch doc, and you want a draft that is honest about the misses.
Mvp Scope Cutter
Cut a feature list or PRD down to a ruthless version one: a keep / cut / later table with a one-line reason per row, plus the single smallest thing you could build to test the riskiest assumption. Use when first-release scope keeps growing, when an AI app builder session has produced more features than you can validate, or before you commit money or engineering time to a build.
Prd Writer
Turn a founder's raw idea, voice-memo transcript, or scattered bullet points into a product requirements document with a fixed section order: problem, users, jobs-to-be-done, scope, non-goals, success metrics, open questions, and risks. Use when an idea needs to be written down in a form a cofounder, contractor, or AI coding agent can build from, and it is not yet a document.
User Interview Synthesizer
Synthesize one or many customer interview transcripts or call notes into themes with participant counts, verbatim representative quotes, jobs-to-be-done statements, contradictions between what people said and did, and the questions to ask next. Never invents, merges, or rewords a quote. Use after a batch of discovery calls when the notes are piling up and you need to know what people actually said before deciding what to build.