💼 Business
Product Manager Prompt: Stories Roadmap From Notes
Paste your PM notes: get user stories, acceptance criteria, a roadmap slice and open questions. Facts only; no invented metrics or customer quotes.
0Reviews
Prompt
Act as a senior product manager who turns messy discovery notes into shippable stories, acceptance criteria and a short roadmap slice. You organize what the user already wrote. You do not invent metrics, customer quotes, personas, competitors, dates or capacity numbers. Inputs: - Product or feature name in the user's words: [ProductName] - Who the change is for, as the user described them: [Audience] - Raw notes from interviews, tickets or docs (paste facts only): [DiscoveryNotes] - Constraints the team already agreed (stack, policy, timeline words they used): [KnownConstraints] - Outcomes the user already measured or hopes to measure, with numbers only if they pasted them: [OutcomesOrMetrics] - Stakeholders who must read the next update: [Stakeholders] - Time horizon the user wants on the roadmap slice (for example next two sprints): [RoadmapHorizon] Generate: 1. Scope line: restate ProductName and Audience in one sentence, and say this is a planning draft from pasted notes, not a committed roadmap. 2. Problem and opportunity: 3 to 5 bullets drawn only from DiscoveryNotes. Mark UNKNOWN where a claim lacks a note. 3. User stories: write 4 to 8 stories in "As a / I want / so that" form using only roles and needs present in DiscoveryNotes or Audience. Number them S1, S2, ... 4. Acceptance criteria: for each story, 3 to 5 Given / When / Then checks that a QA engineer could run. No invented analytics events unless named in the notes. 5. Roadmap slice: group the stories under Now / Next / Later for RoadmapHorizon. Do not assign story points, velocity or calendar dates unless the user supplied them in KnownConstraints. 6. Open questions: list clarifying questions for Stakeholders, tied to gaps in DiscoveryNotes. 7. Stakeholder update draft: a short paragraph a PM could paste into Slack or email, facts only, with a "needs confirmation" line for any UNKNOWN. 8. What you refused: name metrics, quotes, competitors or dates you did not invent. Rules: work only from Inputs. Never invent NPS, conversion rates, persona names, competitor feature lists, sprint capacity or launch dates. If DiscoveryNotes is empty, ask for at least five concrete bullets before writing stories.
Instructions
Paste real discovery notes only. Redact customer names if needed. Variation: ask for a Jira-ready story table. Tip: link your stories to a separate epic breakdown prompt after this draft; never invent metrics the notes lack. TeamPulse is a fictional example; Notion, Slack, Jira and React are trademarks of their owners and PromptDig is not affiliated with them.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
ProductName: TeamPulse weekly check-in for remote squads Audience: Engineering managers at 40 to 200 person B2B SaaS companies who already run 1:1s in Notion DiscoveryNotes: Managers paste Friday wins and blockers into a shared doc; they forget to close loops on blockers; three managers said they want a Monday digest; one said Slack threads get lost; no one asked for AI coaching; security said no storing raw 1:1 notes outside our VPC; design wants a one-screen digest, not a dashboard. KnownConstraints: Must ship inside existing React web app; SSO already live; no new vendor for storage; "try a two-sprint slice" said in planning; analytics events already exist for page_view and button_click only. OutcomesOrMetrics: Hope managers reopen fewer stale blockers; no baseline number pasted yet. Stakeholders: Eng managers pilot group (6 people), Head of Engineering, Security review, Design lead RoadmapHorizon: next two sprints
Example Output
1. SCOPE Planning draft for TeamPulse weekly check-in for remote squads, aimed at engineering managers in mid-size B2B SaaS who already run 1:1s in Notion. This is not a committed roadmap. 2. PROBLEM AND OPPORTUNITY - Friday wins and blockers live in a shared doc today (from notes). - Blockers often lack a clear close-the-loop step (from notes). - Three managers asked for a Monday digest (from notes). - Slack threads are easy to lose (from notes). - Security forbids storing raw 1:1 notes outside the VPC (constraint). - Design wants a one-screen digest, not a dashboard (from notes). - AI coaching: not requested (notes say no one asked). 3. USER STORIES S1. As an engineering manager, I want a Friday check-in form for wins and blockers so that my notes stay in one place inside our app. S2. As an engineering manager, I want each blocker to have an owner and a next step so that open items do not go stale. S3. As an engineering manager, I want a Monday digest of open blockers so that I can prep 1:1s without hunting Slack. S4. As a security reviewer, I want check-in data stored only in our existing VPC-backed store so that raw notes never leave our boundary. S5. As a design lead, I want the digest on one screen so that managers are not pushed into a multi-widget dashboard. 4. ACCEPTANCE CRITERIA (sample for S3) - Given I submitted a Friday check-in with at least one open blocker, When the Monday digest runs (send time UNKNOWN, confirm with the pilot group), Then I see a digest listing those blockers with owner and next step fields. - Given a blocker was marked done on Sunday, When the digest renders, Then that blocker is omitted. - Given I have no open blockers, When the digest renders, Then I see an empty state that says there are no open blockers (exact copy TBD with Design). - Given analytics, When the digest opens, Then only existing page_view fires; no new event names unless product later defines them. 5. ROADMAP SLICE (next two sprints) Now: S1 Friday form, S2 blocker owner/next step, S4 storage in existing VPC store. Next: S3 Monday digest, S5 one-screen digest layout. Later: any coaching or AI summary features (explicitly out of scope per notes). 6. OPEN QUESTIONS - What is the baseline count of stale blockers per manager today? (OutcomesOrMetrics has no number.) - Should the digest email, in-app only, or both? (not in notes) - Who in the 6-person pilot is the first reviewer for empty-state copy? 7. STAKEHOLDER UPDATE DRAFT TeamPulse two-sprint slice focuses on a Friday wins/blockers form, owner + next step fields, VPC-only storage and a Monday one-screen digest for eng managers. Security constraint: no raw 1:1 notes outside our VPC. Needs confirmation: baseline stale-blocker metric and digest channel (email vs in-app). 8. WHAT I REFUSED No invented NPS or conversion rates, no persona names beyond eng managers, no competitor feature list, no story points, no launch calendar date.