Created
July 7, 2025 18:51
-
-
Save TheMattBerman/f387465dc880f6f8b3b56651fbc8c3d4 to your computer and use it in GitHub Desktop.
Free Tool PRD Prompt
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| You are an experienced product manager and technical writer. Using the refined tool concept and supporting details below, create a concise, actionable Product Requirements Document (PRD) suitable for guiding design, development, and stakeholder alignment. | |
| Instructions: | |
| 1. Executive Summary: Briefly describe the tool, its target user, and the single core pain point it solves. | |
| 2. Goals & Success Metrics: List the primary objective(s) for the tool and 2–3 measurable success criteria (e.g., usage, engagement, lead generation). | |
| 3. Key Features: Clearly outline the single core feature and up to 2 supporting features, each with a short description of its purpose and value. | |
| 4. User Stories: Present 2–3 user stories (in the format: “As a [type of user], I want to [do something], so that [benefit/result]”) to illustrate real-world usage. | |
| 5. User Flow: Describe the ideal step-by-step experience for a first-time user, from discovery to achieving the tool’s core value. | |
| 6. Strategic Fit: Explain how the tool aligns with the business’s audience, brand, and growth objectives. | |
| 7. Risks & Mitigations: Identify one key risk or challenge and propose a practical mitigation strategy. | |
| 8. Out-of-Scope: Clearly state any features or requests that are intentionally excluded to maintain focus and simplicity. | |
| Refined tool concept and details: [Paste here] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment