> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trysixth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> Reusable step-by-step instructions you run with a slash command.

Workflows are Markdown files describing a series of steps for Sixth to follow, such as releasing a version, opening a PR or setting up a new service. Save one once, then run it any time with `/filename`.

<Note>
  These are **slash-command workflows** stored as files in your project. They're different from [Workflow integrations](/features/workflow-integrations), which connect Sixth to apps like Gmail, Calendar and Slack.
</Note>

## Creating a workflow

1. Click the **scales icon** in the message box toolbar and open the **Workflows** tab.
2. Under **Workspace Workflows** (this project) or **Global Workflows** (every project), click **New workflow file...**, type a name and press Enter.
3. The file opens in the editor. Write the steps Sixth should take.

Or create the files yourself:

| Scope | Location |
| - | - |
| Workspace | `.sixthrules/workflows/` in your project |
| Global | `Documents/Sixth/Workflows` in your user folder (`~/Documents/Sixth/Workflows` on macOS and Linux) |

Files can be `.md`, `.txt` or have no extension.

## Running a workflow

Type `/` and pick the workflow from the **workflows** section of the menu, or type its full file name, for example `/release.md`. Anything you type after the command is passed along with it:

```
/release.md patch release, skip the changelog
```

Each workflow has an on/off switch in the Workflows tab; turned-off workflows don't appear in the menu. If a workspace workflow and a global workflow have the same name, the workspace one is used.

## Writing good workflows

A workflow can use anything Sixth can do:

* its built-in tools (reading and searching files, editing, `ask_followup_question`, `new_task`, …),
* command-line tools you have installed, like `gh`, `docker` or `npm`,
* [MCP servers](/mcp/mcp-overview) and [workflow integrations](/features/workflow-integrations).

Number the steps, say what to check before moving on, and say when to stop and ask you.

```markdown release.md [expandable] theme={"system"}
# Release a new version

1. Make sure the working tree is clean (`git status`). If it isn't, stop and ask me.
2. Run `npm test`. If anything fails, stop and show me the failures.
3. Ask me whether this is a patch, minor or major release (use ask_followup_question).
4. Run `npm version <type>` to bump the version and create the tag.
5. Add a CHANGELOG.md entry summarising the commits since the last tag.
6. Push the commit and the tag (`git push --follow-tags`).
7. Create a GitHub release with `gh release create` using the changelog entry as notes.
8. Report the new version and the release URL.
```

<Tip>For instructions Sixth should be able to pick up on its own, without you typing a command, write a [skill](/features/skills) instead.</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.