> 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/quickstart/writing-your-first-cues/spikes.md).

# 4.9 Spikes

Instead of just telling it to go to a specific number position, we'll create the cue using a Spike, right from the movement editor.

How about we create a cue from scratch that moves the **Wagon** off stage right?

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-58418dd475b9309a42d8c7a17d6722863efd8c68%2FSM_QS_NS_CueFromScratch.gif?alt=media)

1. **Click "Cue"** from the **Top Menu Bar** and **Select "Add Cue".** Keyboard warriors can use **CTRL + U.**
2. **Add the Wagon** to the cue.
3. **Name** the cue **Wagon Off**, and pick another fun color!
4. Go to the **Edit Movement Window** and click **"Add Spike"**
5. **Double Click** in the new spike's **Name Box** to change the name to **Off SR**
6. While the **Name Box** is active, **Double Click** or **Tab** to move to and edit the **Value Box to 0.**
7. **Press Tab or Enter** to save the value.
8. **Single Click** on the spike to select it. It will **highlight orange** when it's selected.
9. **Click "Update"** to save and close the **Edit Movement Window.**

To learn more about [Spikes:](/docs/spikemark/spikes.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.creativeconners.com/docs/spikemark/quickstart/writing-your-first-cues/spikes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.