Iteration plan | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Sprint goal, capacity plan and prioritized backlog.

Start with: Backlog, estimates, availability and carryover.

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

Define the period's objective and its completion criteria. Review unfinished work and dependencies before accepting new requests.
Estimate usable capacity and effort using the team's own units; do not compare estimates across teams as if they were identical.
Select work that supports the objective and fits the available skills and time. Keep a visible allowance for expected interruptions.
Return selected work, sequencing, owners and deferred items with reasons. Confirm each item has an observable acceptance condition.

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: Match workload to people, budget and priorities.

Possible success measures: On-time milestones, utilization, budget variance. 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: iteration-plan
description: "Prepare sprint goal, capacity plan and prioritized backlog. Use for this workflow with supplied business information."
---

# Iteration plan

## Inputs and purpose

Use this workflow to prepare: Sprint goal, capacity plan and prioritized backlog.

Start with: Backlog, estimates, availability and carryover.

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. Define the period's objective and its completion criteria. Review unfinished work and dependencies before accepting new requests.

2. Estimate usable capacity and effort using the team's own units; do not compare estimates across teams as if they were identical.

3. Select work that supports the objective and fits the available skills and time. Keep a visible allowance for expected interruptions.

4. Return selected work, sequencing, owners and deferred items with reasons. Confirm each item has an observable acceptance condition.

## 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: Match workload to people, budget and priorities.

Possible success measures: On-time milestones, utilization, budget variance. 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).