The PRD Prompt Pack: 11 Claude Prompts
Stop writing PRDs from scratch. Start with prompts that extract the right decisions from your team in minutes, not days....
Free frameworks, templates, checklists, and prompt packs for product managers and founders building with AI. Practical, downloadable, and ready to use.
Stop writing PRDs from scratch. Start with prompts that extract the right decisions from your team in minutes, not days....
Most teams skip straight to solutions. The teams that ship products people actually use spend more time on the problem t...
Most product decisions aren't hard because the data is missing. They're hard because the question being asked is wrong....
Most product teams are great at building. They're bad at deciding. These prompts fix the deciding part. π Read time: 14...
Stop planning what feels productive. Start planning what moves the product. π Read time: 10 minutes. Use time: every sp...
A launch is not an event. It is the moment your product earns the right to be judged by strangers. π Read time: 10 minu...
Most features don't fail because they're bad. They fail because nobody knew they existed, nobody understood why they mat...
A feature that ships without a story is a changelog entry. A feature that ships with the right story is a growth moment....
Most teams treat launch as the finish line. The teams that build traction treat it as the starting gun. π Read time: 10...
Most features fail not in the building. They fail in the 72 hours before and after you ship. π Read time: 10 minutes. U...
Most features get built in weeks and announced in an afternoon. That's backwards. The launch moment is where positioning...
Most products don't fail at launch. They fail in the six weeks before it, when the right decisions get deferred. π Read...
Most AI tools are built for one job. The teams wasting time are the ones treating them like they do all jobs. π Read ti...
Most teams don't fail because they lacked tools. They fail because they picked the wrong tools for the wrong stage, then...
Coding is becoming cheaper. Knowing what to build is becoming more valuable. But you still have to build it. Here's how...
Most early-stage founders are measuring the wrong things with the right tools. The fix isn't better dashboards. It's kno...
Most AI tool reviews tell you what a product does. This framework tells you whether it fits where you actually are, what...
Most AI products die not from bad code but from bad feedback loops. This guide maps the analytics and growth tool landsc...
When code works but the product is broken, most teams debug the wrong thing. These prompts help you debug the right thin...
90% of features ship and die. This framework fixes the 3 decision points where most teams lose the plot. Read time: 14 m...
Most founders track metrics. The ones who raise and scale track the right metrics at the right stage. π Read time: 14 m...
Most founders run experiments to confirm what they already believe. The ones who grow run experiments to find out what t...
Most founders write OKRs that look ambitious on a slide and mean nothing in a weekly standup. The ones that win write OK...
Most teams run experiments to feel productive. The teams that grow run experiments to reduce the cost of being wrong. π...
Most teams prioritize features by whoever argues loudest. The teams that build great products prioritize by what the bus...
Most early-stage founders confuse motion with progress. Running experiments isn't the same as running the right experime...
OKRs fail when they become HR hygiene. They work when they're the operating system for every build decision. π Read tim...
You don't need to become a designer. You need to communicate clearly enough that good design can happen. π Read time: 1...
Most competitive analyses answer the wrong question. They map who exists. This framework maps who matters, why they're w...
Most teams test what they built. The best teams test whether they built the right thing. π Read time: 14 minutes. Use t...
The model isn't the strategy. But picking the wrong one for the wrong job costs you weeks you won't get back. π Read ti...
Code review isn't a quality gate. It's the last moment you have to ask "should this exist at all" before it becomes some...
Code review is the last line of defense before production. Most teams treat it like a style guide check. The teams that...
Most debugging sessions start with a symptom. The ones that end fast start with a hypothesis. β±οΈ Read time: 14 minutes....
Most teams ship and hope. The ones that don't use prompts like these. π Read time: 14 minutes. Use time: every sprint,...
Most teams treat architecture as a technical decision. The teams that build durable products treat it as a product decis...
Most builders are asking "how do I add an agent to my product?" The better question is "does this problem actually need...
Most debugging is just asking the wrong questions in the right order. These prompts ask the right questions first. π Re...