20 One-Shot Prompts: Turn Cline Kanban Into Autonomous Workflows

TL;DR

• Cline released 20 copy-paste prompts that decompose projects into linked task cards for parallel agent execution
• Covers full-stack scaffolding, migrations, testing, auth, DevOps, and infrastructure — each prompt chains dependencies and fans out parallel work
• Install with npm i -g cline, paste a prompt into Kanban sidebar chat, watch agents execute end-to-end workflows autonomously

What Dropped

Cline published a collection of 20 production-ready prompts designed for the Kanban Agent feature. Each prompt decomposes a complex development task into linked subtasks that execute in parallel where possible, creating autonomous workflows that go from a single sentence to committed code. The prompts span five categories: greenfield scaffolding, codebase modernization, testing and quality, feature development, and DevOps.

The Dev Angle

The real insight here: Kanban isn't a project management board. It's an orchestration layer. One prompt in the sidebar chat can create a dependency graph where task 1 triggers tasks 2 and 3 in parallel, which both feed into task 4. This matters because it lets you describe complex workflows in natural language and have multiple agents execute them simultaneously without stepping on each other.

The prompts are structured around linking patterns. A full-stack app with database (prompt 4) sets up Express and SQLite sequentially, then fans out CRUD routes and validation in parallel, with seeding running alongside route development. The authentication system (prompt 13) is more complex: register, login, and middleware build in parallel after the auth module is ready, then route protection converges on all three. GitHub Actions CI/CD (prompt 18) runs the CI workflow, release workflow, and contributing docs in parallel, then adds badges after both exist.

Each prompt is copy-paste ready. No setup required beyond npm i -g cline. The prompts handle TypeScript, testing frameworks (vitest), databases (SQLite), security (bcryptjs, helmet), logging (pino), and infrastructure (Docker, GitHub Actions, Turborepo).

Should You Care?

If you're building new projects or refactoring legacy codebases, these prompts save hours of boilerplate and decision-making. The parallel execution patterns are especially valuable for teams: while one agent sets up the test framework, another writes unit tests and a third writes integration tests — all simultaneously. For infrastructure tasks like Dockerization or CI/CD setup, which are normally tedious and repetitive, Kanban handles the orchestration so you don't have to.

If you're already using Cline for single-file edits or small features, this is a signal to think bigger. The Kanban Agent is designed for end-to-end project workflows, not just code completion. The linking patterns show how to structure complex work so agents can execute it autonomously.

The prompts are starting points. Cline is explicitly asking developers to build their own workflows and share them with #OneShotShip on Twitter/X or in their Discord and Reddit communities. They're also running a $1M open source grant program for tools and integrations built on Kanban.

Getting Started

Install Cline globally, navigate to any project directory, open the Kanban Agent, and paste one of the 20 prompts into the sidebar chat. Start with the greenfield prompts (Express API, React + Vite, CLI tool) if you're building from scratch. If you're modernizing existing code, try the JavaScript-to-TypeScript migration or dependency audit. For infrastructure, the GitHub Actions CI/CD and Dockerization prompts are production-ready.

The most complex prompt is the authentication system (prompt 13), which demonstrates how Kanban handles convergence: three parallel branches (register, login, middleware) that all feed into route protection. This pattern is reusable for any feature with multiple independent subtasks that need to converge.

Source: Cline