Write spec | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Requirements document and acceptance criteria.

Start with: Problem, user needs, evidence and constraints.

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 problem, users, desired outcome and evidence for doing the work. State what is outside the scope.
Describe the required behavior, inputs, outputs, constraints and relevant exception paths.
Write observable acceptance criteria and identify dependencies or unresolved decisions that can change the implementation.
Return a requirements document suitable for review. Check that criteria test user outcomes rather than merely repeating a feature list.

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: write-spec
description: "Prepare requirements document and acceptance criteria. Use for this workflow with supplied business information."
---

# Write spec

## Inputs and purpose

Use this workflow to prepare: Requirements document and acceptance criteria.

Start with: Problem, user needs, evidence and constraints.

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 problem, users, desired outcome and evidence for doing the work. State what is outside the scope.

2. Describe the required behavior, inputs, outputs, constraints and relevant exception paths.

3. Write observable acceptance criteria and identify dependencies or unresolved decisions that can change the implementation.

4. Return a requirements document suitable for review. Check that criteria test user outcomes rather than merely repeating a feature list.

## 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).