Anatomy of a guide
Each guide follows the same structure so you can scan quickly, build safely, and verify the result before real users depend on it.
Standard structure
| Section | What it answers |
|---|---|
| Outcome | What business result this guide is meant to produce. |
| Before you start | What workspace access, source documents, channels, or integrations you need. |
| Build steps | Which agent, knowledge base, skill, interface, trigger, or channel to configure. |
| Test prompts | Realistic examples to run before publishing. |
| Verification | How to know the workflow is producing the right result. |
| Rollout notes | What to monitor after users start using it. |
How to read a guide
Read the outcome and prerequisites first. If those match your need, follow the build steps in order. Do not skip the verification section, especially for guides that send messages, call tools, or use external integrations.
How to adapt a guide
Keep the workflow pattern and replace the team-specific details: agent instructions, knowledge sources, approval rules, integrations, and final delivery channel.