> For the complete documentation index, see [llms.txt](https://doc.aissist.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.aissist.io/tutorial/aissist-build-checklist.md).

# Aissist Build Checklist

*Last updated: May 15, 2026*

Use this checklist before you test or deploy a new Aissist workflow.

### Instructions and context

Make sure you:

* keep global instructions short and direct
* put workflow-specific rules in sub agents
* put shared business facts in workspace context
* avoid mixing facts, tone, and workflow logic in one long instruction

See [Tune Aissist Behavior](/tutorial/tune-aissist-behavior.md) for the instruction model.

### Assets

Make sure you:

* add the sources Aissist needs for the workflow
* remove outdated or conflicting information
* include the exact details users need to complete the task
* verify retrieval with [Asset Debugger](/tutorial/turn-assets-into-ai/asset-debugger.md)

See [Turn Assets into AI](/tutorial/turn-assets-into-ai.md) for asset setup.

### Actions

Make sure you:

* name each action clearly
* describe what it does and when it should run
* define parameters with clear names and guidance
* test action inputs and outputs with [Action Debugger](/integrations/action-debugger.md)

Use actions when the workflow needs live data or system changes.

### Sub agents

Make sure you:

* define one clear scenario for each sub agent
* link only the assets and actions needed for that workflow
* set the right reply, handoff, no response, or close behavior
* add summary or acknowledgement only when the workflow needs it

See [Create Sub Agents](/tutorial/create-sub-agents.md) for setup details.

### Test before deployment

Make sure you:

* test thoroughly in [Simulator](/tutorial/simulator.md)
* use realistic input context, such as email or order number, when needed
* review output context, triggered sub agents, and action calls
* fix issues at the source, then test the same scenario again

### Deploy safely

Make sure you:

* start with one narrow managing point
* enable the right operating mode for the workflow
* run **Auto-Pilot** for a short period first
* review live results before expanding coverage

See [Deploy Gateway](/tutorial/deploy-gateway.md) for deployment setup.

### Best practice

Build one repeatable workflow first.

Test it, monitor it, then expand to the next workflow.