Skip to main content

Workflows

What is the Workflows feature?​

The Workflows feature allows you to save repeated prompts and manually use them when appropriate. A workflow is a simple Markdown file that you add to your prompt via the input area. This allows you to reuse effective pipelines and boost your productivity.

A workflow can also be either global or local:

  • Global workflows are stored in .explyt folder in your home directory and shared across all projects on your local machine.
  • Local workflows are stored in .explyt folder in your project directory and visible only in that project. You can commit some of the project workflows via VCS if you want to share effective workflows with your colleagues.

To create a workflow, follow these steps:

  • Open a new chat
  • Open the workflow creation dialog
  • Enter a filename, choose whether the workflow is local or global, and press OK
  • In the opened file, put the Markdown content of your workflow

To add a workflow, simply start typing #workflow in the input area and a hint with available workflows will appear.

Best practices​

Here are some tips for improving your experience when using workflows:

  • Instruct the agent to ask you appropriate questions before moving to the implementation
  • Instruct the agent on how to gather context for the request
  • Specify the expected steps the agent should take
  • You can attach files to your request and reference them in your workflow
  • Keep workflows reusable by using placeholders (for example: {goal}, {files}) and filling them when invoking

Examples​

Workflow that asks the agent to find all TODOs in the attached files and implement them.

Goal: Find and implement TODOs in the attached files (and the currently open file, if relevant).

Scope:
- Operate only on the attached files and the currently open file. If broader changes are needed, ask first.

Steps:
1) Parse the provided files and list all TODOs with file path and line number.
2) Group TODOs by file/subsystem and identify dependencies or ordering.
3) Ask clarifying questions for ambiguous TODOs (owner intent, constraints, acceptance criteria).
4) Propose a minimal, safe implementation plan with a file-by-file edit list and request approval.
5) Implement TODOs, keeping changes small and focused. Avoid unrelated refactoring.
6) After edits, summarize changes (files touched, key decisions, potential follow-ups).

Output:
- TODO Inventory: table/bullets with file:line and short description.
- Questions (if any): bullets.
- Plan (pending approval): numbered steps.
- Edits: apply once approved, then provide a brief summary.

Workflow that asks the agent to add comments to the currently open file.

Goal: Improve code readability by adding concise, accurate comments without changing behavior.

Scope:
- Only modify the currently open file unless the user approves changes elsewhere.

Steps:
1) Read the entire file to understand purpose, public API, and complex logic.
2) Draft a commenting plan: file/header comment (if lacking), function/class doc comments, and inline comments for non-obvious logic or invariants.
3) Ask about style preferences if unclear; otherwise follow the project's existing conventions.
4) Apply comments, keeping them precise and avoiding restating obvious code.
5) Provide a short summary of what was commented and why.

Constraints:
- Do not change program logic or formatting beyond what's necessary for comments.
- Keep comments brief (1–3 lines typically) and maintain consistent tone.

Output:
- Comment Plan (brief)
- Applied changes summary with rationale