Claude for Product Managers
Your Prompt Library: Build It As You Go
The core principle is simple: don't build a library in anticipation of work, build it from work you've already done well.
Start With Output, Not Intent
Most people build prompt libraries the wrong way. They sit down on a Sunday, create folders, write hypothetical templates, and end up with a graveyard of prompts they never touch. The better method: work normally, and when Claude produces something that genuinely nails it (the right tone, the right structure, the right depth), stop and save that prompt immediately.
Four to six weeks of this discipline produces something a planned library never could: a collection shaped entirely by your real workflow.
| Folder | What Lives There |
|---|---|
/first-drafts | PRDs, memos, briefs, proposals |
/synthesis | Interview summaries, research digests |
/pressure-testing | Critique prompts, devil's advocate reviews |
/communication | Stakeholder updates, escalation notes |
The Template Standard
Every saved prompt becomes a reusable template with bracketed placeholders replacing one-time context.
Example: Stakeholder Update:
"Write a stakeholder update for [PROJECT NAME]. Current status: [STATUS]. Key decisions made: [DECISIONS]. Risks to flag: [RISKS]. Audience is [AUDIENCE] who care most about [THEIR PRIORITY]."
The bracket discipline forces you to notice what actually varies each time and what stays constant.
The Compounding Effect
A prompt library built this way gets more valuable the longer you use it. Each saved prompt is proof the format works. You stop writing from scratch, reduce inconsistency across your outputs, and build something that genuinely reflects how you think and work. That is something no pre-made template pack can replicate.