Jira Epic Roadmap Summary for Stakeholders
Turn epics and dates into a clear quarterly view.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Summarise epics for a stakeholder roadmap. Epics with goal, owner, status, percent complete as shown in Jira, target dates and key risks: [EPIC_LIST]. Audience and their questions: [AUDIENCE]. Quarter: [QUARTER]. Write three headline messages in the style 'Checkout redesign is on track for Q2; the payments integration is at risk because the supplier has not confirmed the test date.' Then a table of epics grouped by theme with status, a plain-language outcome for each, dates and confidence, risks and decisions needed (Risk, Epic, Impact, Mitigation, Decision needed by), and what is out of scope. Status rules: on track means no known blocker and progress consistent with dates; at risk means a risk exists with a plan; late means the date will be missed without a change. Use only my numbers, and show percentage complete as resolved issues divided by all issues (18 of 30 is 60 percent), cautioning that it ignores effort [VERIFY]. Offer a six-line slide with three columns (now, next, later), an email of 120 words, and the five questions the audience will ask with a one-sentence honest answer each. Dates beyond the next quarter are indicative, without false precision. Explain confidence in three sentences and say how often the roadmap changes and how stakeholders will be told. Tag uncertain tool details [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.