PM PM Craft Studio Subscribe Free

AI-native product management

Prompts, templates, and automations for product leaders who carry a lot.

A warm, practical workspace for senior PMs and product teams to move from manual coordination to repeatable AI-assisted operating systems.

Join the free subscriber list Browse usable templates

Product

A library built around the real week of a product manager.

PM Craft Studio packages interoperable prompts, templates, and lightweight automation playbooks that work across ChatGPT, Claude, Gemini, Copilot, Notion, Slack, email, docs, and calendar systems.

Strategy

PRDs, outcomes, and decisions

Crystal-clear structures for documenting problem framing, success metrics, tradeoffs, decision records, and product outcomes.

Execution

Epics and acceptance criteria

Prompt groups that turn messy notes into crisp epics, user stories, ACs, risks, dependencies, and release checklists.

Influence

Executive and GTM narratives

C-suite slide structures, enablement outlines, launch plans, customer-facing narratives, and go-to-market templates.

Operations

Personal PM operating system

Meeting notes, action tracking, follow-ups, reminders, Slack triage, email review, and calendar hygiene workflows.

Templates

Copy-ready starters for repeatable product work.

Every template is intentionally system-neutral. Replace bracketed fields, paste into your preferred AI tool, and keep the output in your team workspace.

Personal organization package

Weekly PM command center

Turns scattered tasks, meetings, and loose promises into a single weekly plan.

How to use it

  1. Copy this into any LLM, such as ChatGPT, Claude, Gemini, Copilot, or your company-approved AI tool.
  2. Replace every bracketed field with your real weekly context, including meetings, deadlines, goals, and people waiting on you.
  3. Move the final task list into your task manager, calendar, or weekly planning doc, then ask the AI to revise it if priorities feel wrong.
Create my weekly PM command center using this input:
Role: [your role]
Top goals this quarter: [goals]
Meetings this week: [meetings]
Open decisions: [decisions]
Known deadlines: [deadlines]
People waiting on me: [names/items]

Return:
1. My top 5 priorities
2. A task list grouped by Now, Next, Later
3. Follow-ups I owe
4. Risks or blocked work
5. Calendar changes I should consider
6. A short Monday planning note I can send to myself
Meeting notes and action items

Notes to tasks converter

Converts raw notes into decisions, owners, due dates, and follow-up reminders.

How to use it

  1. Paste this prompt into your AI tool immediately after a meeting, then add raw notes from Zoom, Google Docs, Notion, Apple Notes, or handwritten notes you typed up.
  2. Fill in the meeting name, date, attendees, and preferred task system so the output is formatted for where you actually work.
  3. Review owner names and due dates before sharing, then paste the action items into Jira, Asana, Linear, Todoist, Notion, or your follow-up email.
Convert these meeting notes into an action system:
Meeting: [name]
Date: [date]
Attendees: [people]
Raw notes: [paste notes]

Return:
1. Summary in 5 bullets or fewer
2. Decisions made
3. Action items with owner, due date, and next step
4. Open questions
5. Risks or dependencies
6. Follow-up message drafts for each owner
7. Tasks formatted for [Asana/Jira/Todoist/Notion/other]
PRD

Senior PM PRD builder

Creates a decision-ready PRD from discovery notes, goals, and constraints.

How to use it

  1. Use this in an LLM when you have a rough product idea, discovery notes, customer evidence, or a draft brief that needs structure.
  2. Replace the bracketed fields with real context. Include messy notes if that is all you have, but label assumptions clearly.
  3. Paste the output into your PRD doc, then run a second pass asking the AI to identify gaps, weak evidence, risks, and open decisions.
Act as a senior product partner. Draft a PRD from:
Problem: [problem]
Target users: [users]
Business goal: [goal]
Customer evidence: [research, tickets, data]
Constraints: [technical, legal, operational]
Non-goals: [scope boundaries]
Metrics: [success measures]

Use this structure:
1. Executive summary
2. Problem and evidence
3. Goals and non-goals
4. User journeys
5. Requirements
6. Risks, assumptions, dependencies
7. Launch and measurement plan
8. Open decisions
Epic and AC creation

Epic decomposition prompt

Breaks a PRD or initiative into epics, stories, acceptance criteria, and QA notes.

How to use it

  1. Paste this into your AI tool after you have a PRD, initiative brief, or agreed product scope.
  2. Replace the bracketed fields with the initiative name, PRD content, design status, engineering constraints, and expected release timing.
  3. Review the generated epics with engineering and design, then copy approved stories and acceptance criteria into Jira, Linear, Azure DevOps, or your delivery tracker.
Transform this product initiative into delivery-ready epics:
Initiative: [name]
PRD or brief: [paste]
Engineering constraints: [constraints]
Design status: [status]
Release target: [date or milestone]

Return:
1. Epic list with user value and priority
2. User stories for each epic
3. Acceptance criteria in Given/When/Then format
4. Edge cases and error states
5. Analytics events
6. Dependencies and sequencing
7. QA checklist
Executive slides

C-suite product narrative

Frames a concise executive update with crisp recommendations and decisions.

How to use it

  1. Use this before building slides in Google Slides, PowerPoint, Keynote, or a doc-based executive memo.
  2. Replace each bracketed field with the audience, decision needed, current status, metrics, risks, and your recommendation.
  3. Turn the outline into slides, then ask the AI to tighten the story for executive clarity, decision quality, and time-boxed presentation length.
Create an executive presentation outline:
Audience: [executives]
Decision needed: [decision]
Product area: [area]
Status: [status]
Key data: [metrics]
Risks: [risks]
Recommendation: [recommendation]

Return 8 slides:
1. Title and decision ask
2. Why this matters now
3. Customer and business evidence
4. Options considered
5. Recommendation
6. Investment and tradeoffs
7. Risks and mitigations
8. Next steps and owners
Decision record

Product decision log

Captures context, rationale, owners, reversibility, and follow-up measurement.

How to use it

  1. Paste this into your AI tool after a product, design, engineering, customer, or leadership decision has been made.
  2. Replace the bracketed fields with the decision, stakeholders, options considered, evidence, and any unresolved concerns.
  3. Save the output in your team wiki or product archive, then share the summary with stakeholders so the decision is easy to find later.
Document this product decision:
Decision: [decision]
Date: [date]
Owner: [owner]
Stakeholders: [people]
Context: [background]
Options considered: [options]
Data used: [data]

Return:
1. Decision summary
2. Rationale
3. Tradeoffs accepted
4. What would change the decision
5. Communication plan
6. Follow-up metric and review date

Skills and Automation

Packages that help PMs reduce weekly manual work.

01

Slack signal system

Channel taxonomy, saved searches, decision capture, escalation routing, and digest prompts.

02

Email triage loop

Rules for newsletters, stakeholder requests, customer escalations, follow-ups, and weekly summaries.

03

Calendar operating cadence

Meeting audit prompts, focus blocks, recurring review rituals, and automated prep notes.

04

Accountability tracker

Owner mapping, reminder drafts, overdue follow-ups, and status rollups for cross-functional work.

Community Uploads

Crowd-sourced prompts, skills, and agent templates with a relevance review.

Subscribers can submit their own materials. The form uses a simple audit rubric before anything is considered for publishing.

Publishing audit

About

Built by and for product managers who want more leverage without losing judgment.

PM Craft Studio is designed for the PM who owns strategy, execution, coordination, communication, and the quiet glue work that keeps teams moving. The goal is not to replace PM craft. It is to make the repetitive parts lighter so the human judgment has more room.

Contact

Partnerships, feedback, and early access.

Use this for collaborations, subscriber questions, sponsorships, and template requests.

Help and Feedback

Make the library easier to trust, adapt, and share.

Interoperability standard

Templates avoid vendor-specific syntax unless labeled. Inputs, outputs, assumptions, and review steps are written plainly so they can move between tools.

Feedback loop

Subscribers can rate templates, request new use cases, flag unclear instructions, and suggest system-specific variants.

Future paid tiers

Planned subscriptions can include premium packs, team libraries, workshops, review clinics, automation recipes, and private community access.