ADL cheat sheet
| Element | Example |
|---|---|
| UseCase Name Unique, lowercase, underscores. | ### UseCase: password_reset |
| Description Customer situation or query. | #### DescriptionCustomer has forgotten their password and needs to reset it. |
| Steps (optional) Sequence of actions before solution. | #### Steps- Ask for registered email - Send reset link |
| Solution Main recommended fix. | #### SolutionGuide the customer through the reset process at https://www.example.com/reset-password. |
| Alternative Solution (optional) Backup if main fails. | Try login recovery flow using phone number. |
| Fallback Solution (optional) Last resort, avoids loops. | #### Fallback SolutionIf no access to email, escalate to Tier 2 support. |
| Examples (optional) Queries that trigger this use case. | #### Examples- I forgot my password - Can’t log in |
⚡ Advanced Features
Conditionals
Similar to if conditionals, they let you tailor responses based on context.
#### Solution
<isBusinessCustomer> Provide https://example.com/business/reset
Provide https://example.com/reset. <isPrivateCustomer>
Tool Calls
Calls or enforces external functions.
#### Solution
Call @password_reset_link()! to generate a reset link.
Use Case References
Reuse existing flows, stay modular.
#### Solution
If business customer, follow #business_customer_support
✅ Workflow in 15 minutes:
- Define a Use Case.
- Add Steps, Solution, Fallback.
- Use Conditionals for variations.
- Add Tool Calls for actions.
- Reference other use cases for modularity.
- Test → Refine → Deploy.
👉 With ADL, engineers wire the engine once → business defines use cases forever after.