Cline Workflows: Stop Repeating Instructions to Your Agent

TL;DR

• Cline now supports workflows — reusable markdown instruction files invoked with slash commands
• Write a procedure once, execute it repeatedly without re-explaining steps
• Real example: a 30-minute dashboard build becomes a single `/weekly-dashboard.md` command

What Dropped

Cline introduced workflows, a feature that lets you define multi-step procedures as markdown files and invoke them with slash commands. Instead of repeating the same instructions every time you need a task done, you write the process once and call it back with /workflow-name.md. Cline reads the file, adds the steps to its focus chain, and executes with built-in verification.

The Dev Angle

Workflows capture the exact steps you'd normally walk an agent through. A PR review workflow, for example, defines: gather PR info via gh CLI, examine modified files, analyze for bugs and security issues, ask for confirmation, then execute the review. Type /pr-review.md, provide the PR number, and Cline handles the entire 15-minute manual process in one command.

The real power emerges from repetitive domain work. A YC founder mentioned in the announcement maintains 20+ task-family workflows: integrations-slack.md, bug-class-auth.md, migration-postgres.md. Each includes validation, performance checks, and acceptance criteria. The result: significant time savings, near-zero rework, and the ability to parallelize work across multiple agent instances.

Workflows live in .clinerules/workflows/ for project-specific tasks or ~/Documents/Cline/Workflows/ for global ones. Project workflows take precedence when names match.

Should You Care?

If you're running Cline for repetitive tasks — weekly reports, PR reviews, test suites, deployments, project setup — workflows eliminate the friction of re-explaining the same process. You get back time and reduce the chance of missed steps.

If you're using Cline for one-off exploratory work, workflows add minimal value. But if you've found yourself saying "I'll need to do this again next week," that's your signal to build a workflow.

The workflow-building process itself is straightforward. There's even a /create-new-workflow.md meta-workflow that guides you through it. The best approach: after completing a task you know you'll repeat, tell Cline "Create a workflow for the process I just completed." It analyzes the conversation, extracts the steps, and generates the file. Your accumulated context becomes reusable automation.

Start with your most annoying repeated task this week. Include verification steps, handle failures gracefully, and watch your agent shift from assistant to executor. The prompts repository has examples, but your best workflow solves your specific problem.

Source: Cline