Specs, user stories, customer feedback, research and release notes. 9 reviewed prompts for product.
Product managers turn rough ideas and scattered feedback into documents a team can act on. The prompts and skills here help with one-pagers and requirements, user stories with acceptance criteria, themes in customer feedback, interview guides, prioritization and release notes customers will actually read. Feed them real evidence, such as quotes and data, so the output reflects what users said rather than assumptions.
Turns a rough feature idea into a one-page brief: the problem, who has it, the proposed solution, scope limits, risks and how success is measured. Use before asking a team to estimate or design anything.
Defines how you will know a new feature worked: one main measure, supporting and guardrail measures, targets, how to collect them and when to review. Use while planning a feature, before it is built.
Structures a short, blame-free review after a feature has been live for a few weeks: results against goals, what went well, what did not and decisions to keep, change or remove it. Use two to eight weeks after a launch.
Drafts a warm, honest reply to a customer who asked for a feature, whether the answer is yes, not now or no, with a workaround where one exists. Use when you need to answer requests without overpromising.
Compares how a few competitors handle one feature or workflow, using only the facts you provide, and draws out options and a recommendation for your product. Use when deciding whether and how to build something others already offer.
Sorts a pile of raw user feedback (survey answers, reviews, tickets) into clear themes with counts, quotes and a suggested next step for each. Use when feedback has piled up and you need to see what matters most.
Builds a 30-45 minute customer interview guide around one question you need answered, with warm-up, story-based questions, follow-ups and what to avoid asking. Use before talking to customers about a problem or new idea.
Builds a dated launch checklist for a new feature across product, support, marketing, sales and operations, with owners by role and a go/no-go list. Use two to four weeks before a release.
Reads a product requirements document (PRD) and points out missing pieces, vague requirements, untested assumptions and open questions, ranked by how much they could hurt the project. Use before sign-off or handover to design and engineering.
