GPT Tasks/Create a Product Roadmap
Task library

Work · GPT Task

Create a Product Roadmap

Turn product outcomes, customer evidence, opportunities, constraints, and dependencies into a prioritized roadmap with themes, initiatives, horizons, success measures, assumptions, and decision notes.

Context → structured prompt → explicit AI handoff

Runs in this browser. No upload by this page. External AI handoff is explicit. Review before sharing.

Prompt workbenchConfigure → review → use
01

Configure task

Setup
Describe the product, current stage, strategic goals, target outcomes, and the problems the roadmap should address.
Provide verified feedback, usage evidence, requests, research notes, business priorities, or opportunity statements that should inform prioritization.
Prompt style
Additional options
Add known effort signals, team/resource limits, technical dependencies, deadlines, policy constraints, or commitments.

What you’ll need

  • Product goals plus the customer, product, or business evidence you want the roadmap to use
  • Product context and desired outcomes
  • Customer evidence and opportunities

What you’ll get

  • Product outcome frame
  • Evidence and opportunity summary
  • Roadmap themes
  • Prioritized initiatives or candidate bets
  • Horizon placement and rationale
02

Prompt preview

Editable

Review or edit the generated prompt before you copy it or explicitly open an AI chat.

Export

ChatGPT opens with the current prompt prepared. Gemini copies the current prompt, then opens Gemini so you can paste it. Keep secrets and sensitive information out of URL-carried prompts.

Task referenceExamples, expected output, boundaries, and routing.

Examples

1. Early SaaS roadmap

Context: A small SaaS team supplies customer interviews, support themes, usage observations, strategic goals, and limited engineering capacity.

Goal: Build a Now/Next/Later roadmap without manufacturing demand or effort estimates.

Useful output: Outcome frame, themes, prioritized initiatives, evidence gaps, dependencies, measures, and decision notes.

2. Internal operations product

Context: An internal tools team supplies employee pain points, required integrations, policy constraints, and a quarter goal.

Goal: Prioritize improvements while keeping technical effort assumptions visible.

Useful output: Roadmap themes, initiative order, dependencies, provisional horizon, validation needs, and next actions.

3. Creator software roadmap

Context: A solo builder provides user feedback, current feature usage, revenue priorities, and a short list of candidate improvements.

Goal: Decide what to explore next without overpromising timing.

Useful output: Prioritized themes, candidate bets, evidence gaps, success measures, and learning plan.

Expected output

  • Product outcome frame
  • Evidence and opportunity summary
  • Roadmap themes
  • Prioritized initiatives or candidate bets
  • Horizon placement and rationale
  • Dependencies and constraints
  • Success measures and learning questions
  • Assumptions and evidence gaps
  • Decision log and next actions

Truth boundary

Do not invent customer evidence, market demand, engineering effort, dates, dependencies, resources or business impact. Label prioritization criteria and assumptions and keep roadmap timing provisional unless supplied.

Overlap guard: Owns strategic product outcomes, evidence, prioritization, initiatives, and horizons. Use Project Plan for project execution, Startup Business Plan for the broader venture, Project Risks for risk treatment, Status Update for reporting current work, and Agile Sprint for near-term backlog commitment.

Privacy and handoff

Runs in this browser. No upload by this page. Copy/download locally or explicitly open ChatGPT or Gemini. Source files are attached in the chosen AI service, not uploaded by Mycelgrid. Review the generated prompt and AI output before using or sharing it.