Query draft | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Query text and explanation; execution optional.

Start with: Supplied schema, query language and dialect and data request.

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

Clarify the desired result, schema, relationships, date logic and target query language. Ask for missing field definitions before inventing them.
Draft a read-only query at the required grain with explicit joins, filters, aggregation and null handling.
Explain assumptions and a test using sample rows or manually checkable totals. Identify any dialect-dependent syntax.
Return query text and validation notes. Execution is optional and requires actual authorized access; do not confuse a drafted query with a verified result.

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: Make business analysis more trustworthy and repeatable.

Possible success measures: Data completeness, reporting hours, calculation errors. 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: query-draft
description: "Prepare query text and explanation; execution optional. Use for this workflow with supplied business information."
---

# Query draft

## Inputs and purpose

Use this workflow to prepare: Query text and explanation; execution optional.

Start with: Supplied schema, query language and dialect and data request.

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. Clarify the desired result, schema, relationships, date logic and target query language. Ask for missing field definitions before inventing them.

2. Draft a read-only query at the required grain with explicit joins, filters, aggregation and null handling.

3. Explain assumptions and a test using sample rows or manually checkable totals. Identify any dialect-dependent syntax.

4. Return query text and validation notes. Execution is optional and requires actual authorized access; do not confuse a drafted query with a verified result.

## 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: Make business analysis more trustworthy and repeatable.

Possible success measures: Data completeness, reporting hours, calculation errors. 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).