> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark-6/triggers/stacking-triggers.md).

# Stacking Triggers

Triggers can be stacked to form more sophisticated triggers. Stacking triggers is just like [adding triggers](/docs/spikemark-6/cues/cue-creation/add-triggers.md) to a step. Some examples of useful stacked triggers are:

## Complete and Delay

<figure><img src="/files/M1T4FK9rPOdircE4QIfO" alt="Stacked complete and delay trigger"><figcaption></figcaption></figure>

This is handy when you want everything to finish then wait for some time before starting the next step.

## Delay and Position

<figure><img src="/files/MCT5eQWJyVPVQNZunNA5" alt="Stacked delay and position trigger"><figcaption></figcaption></figure>

This is handy when you want to ensure motion has started in the desired direction before looking to see if the motor has crossed the watch position.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.creativeconners.com/docs/spikemark-6/triggers/stacking-triggers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
