Skip to main content
Workflows are Markdown files that define a series of steps to guide the Agent through complex or repetitive tasks. Type / followed by the workflow filename in the editor to invoke one — for example, /bookcover.md. Writing is a multi-stage process, and each stage can be broken down into smaller steps to achieve better results. Drafting an outline, expanding it into a volume plan, then refining each batch of chapters through four or five quality passes — each of these tasks involves remembering a dozen steps, working in the right order, and updating files one by one. Miss a step and you start over. Workflows turn these multi-step processes into a single command. Type /chapteroutline.md and the Agent loads your story settings, produces chapter outlines, and waits for your confirmation before continuing. Every subsequent batch reuses the same command. You just review and decide.

​
Invoking a workflow

Type / in the chat input and SoloEnt shows all available workflows. Keep typing to filter by filename — /book will match bookcover.md. Select a workflow and press Enter to start it. Typing /bo in the chat input, with autocomplete showing the matching bookcover.md workflow The Agent executes each step in sequence, pausing when it needs a decision from you. You can stop a workflow at any point in the conversation.
After completing a new task, tell the Agent: “Turn the process we just went through into a workflow file.” The Agent analyzes the conversation, extracts the steps, and generates the workflow file. Experience you’ve built up becomes reusable automation.

​
Where workflows live

Workflows can be stored in two locations: your writing project directory or a system-level global directory. Global workflows are stored in the system-level directory and are available across all projects. Use them for general-purpose processes like cover prompt generation, standard manuscript review checklists, or publishing prep. Workspace workflows live in .soloent/workflows/ at your project root. Use them for processes tied to a specific project — the pacing logic for this book’s chapter outlines, or the quality checks specific to this series.
When a global and workspace workflow share the same name, the workspace workflow takes precedence.

​
Toggling workflows

Every workflow has a toggle to control whether it appears in the / menu, without deleting the file. Workflows never run on their own — they only execute when you invoke them with a command.

​
Creating a workflow

Workflows panel showing a list of global workflows (bookcover.md, chapteroutline.md, outline.md) with toggle, edit, and delete controls for each
1

Open the Workflows menu

Click the fourth icon from the left in the Agent panel，and switch the Workflows manager.
2

Create a new workflow file

Click “New workflow file…”, enter a filename (e.g., bookcover) and click on ”+”. The file is created with a .md extension.
3

Write your workflow steps

Add a title and steps in Markdown format. Describe what each step should accomplish.

​
Workflow structure

A workflow is a Markdown file with a title and numbered steps. The filename is the command: bookcover.md is invoked with /bookcover.md. Steps can be written at different levels of detail:
  • High-level instructions: “Analyze the novel outline and extract the protagonist’s character traits” — let the Agent decide how to execute
  • Precise control: Use specific format requirements or templates — when you need a fixed output

​
What workflows can contain

​
Natural language instructions

Write steps in plain language and the Agent will interpret and execute them:
This approach works well when the logic is clear but the execution details need the Agent to adapt.

​
Precise template control

When you need a fixed output format, embed the template directly in the workflow:

​
Example workflows

​
Book cover prompt generation

This workflow reads the novel first before generating a cover prompt, so the result reflects the story’s actual tone rather than a generic description.

​
Batch chapter outline generation

This workflow breaks a novel’s chapter outlines into manageable batches. Each batch is confirmed before moving on, so you’re never handed more than you can review at once.

​
Writing effective workflows

  • Start simple. Write steps in natural language first. Only add precise templates when you need a fixed output format.
  • Be explicit about decision points. If a step requires a choice from you, state it clearly: “Wait for the author to confirm before continuing.”
  • Specify failure handling. Tell the Agent what to do when something is missing: “If the information is incomplete, ask the author — do not assume.”
  • Keep workflows focused. bookcover.md handles covers. chapteroutline.md handles chapter outlines. Split complex processes into separate workflows that can run independently.
Workflows execute with your permissions and can read and modify your project files. Review a workflow’s contents before running it, especially if it comes from an external source.

​
Workflows vs. Commands

The built-in commands (/review, /market) are workflows SoloEnt ships out of the box, designed by writing specialists and ready to use without any setup. Workflows are ones you define yourself, fully customized to your project and process. The two complement each other: use built-in commands for standardized quality checks, and custom workflows to automate what’s unique to your writing process.

​
Troubleshooting

Check the following:
  • The workflow must be toggled on in the Workflows panel — toggled-off workflows are hidden from the menu
  • The file must have a .md extension and be located in either the global workflows directory or your project’s .soloent/workflows/ folder
  • If you just created the file, try closing and reopening the panel to refresh the list
The Agent advances automatically unless explicitly told to wait.
  • Add a clear pause instruction at every decision point: “Wait for the author to confirm before continuing”
  • Avoid writing steps as a continuous block — break them into distinct numbered sections so the Agent treats each as a separate stage
  • If a step is being skipped entirely, check whether its instructions are reachable (not buried inside a template block the Agent misread as an example)
Most likely cause: The file paths in the workflow don’t match your actual project structure.
  • Use relative paths from the project root (e.g., SOLOENT.md, chapters/ch-01.md)
  • If the workflow reads SOLOENT.md and the file doesn’t exist yet, the Agent may fail silently — add a fallback instruction: “If SOLOENT.md is missing, ask the author for the required information”
  • Workspace workflows run in the context of the open project folder — make sure the correct project is open when you invoke the command
Workspace workflows take precedence — but only if the names match exactly.
  • Check that the filename (including extension) is identical: chapteroutline.md vs chapteroutline.md
  • A single character difference in the name means both workflows exist independently and neither overrides the other
  • Verify the workspace workflow is saved in .soloent/workflows/ at the project root, not in a subdirectory
Workflows run with your full permissions and can read and modify any file in your project.
  • Review the workflow’s steps before running it, especially if it came from an external source
  • If an unexpected file was modified, check whether any step contains a broad instruction like “update all chapter files” — make the scope explicit
  • For workflows that write output files, specify the exact target path in the step to prevent the Agent from choosing its own location

​
More Advanced Tips

Commands

Learn about SoloEnt’s built-in /review and /market commands

Rules

Capture your writing habits in Rules to use alongside your workflows