Roadmap update | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Prioritized roadmap and change rationale.

Start with: Initiatives, priorities, dates, capacity and dependencies.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Reconcile current initiatives, goals, commitments, capacity and dependencies at the chosen review date.
Assess each initiative's contribution and remaining uncertainty before assigning priority.
Sequence work within actual constraints, distinguishing firm commitments from tentative timing and recording the effect of changes.
Return a roadmap and decision log. Check that priority changes do not silently conflict with externally committed dates or shared resources.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Compare initiatives and investments using explicit assumptions.

Possible success measures: Milestone delivery, actual benefit, payback and return. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: roadmap-update
description: "Prepare prioritized roadmap and change rationale. Use for this workflow with supplied business information."
---

# Roadmap update

## Inputs and purpose

Use this workflow to prepare: Prioritized roadmap and change rationale.

Start with: Initiatives, priorities, dates, capacity and dependencies.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Reconcile current initiatives, goals, commitments, capacity and dependencies at the chosen review date.

2. Assess each initiative's contribution and remaining uncertainty before assigning priority.

3. Sequence work within actual constraints, distinguishing firm commitments from tentative timing and recording the effect of changes.

4. Return a roadmap and decision log. Check that priority changes do not silently conflict with externally committed dates or shared resources.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Compare initiatives and investments using explicit assumptions.

Possible success measures: Milestone delivery, actual benefit, payback and return. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).