What is dev_workflow?

A set of rules for managing software work with Taskmaster, a task-management workflow for development projects. It organizes work by listing tasks, choosing the next one, showing details, breaking down complex tasks, recording progress, and marking work complete.

Use it to review pending work, select the next task, expand large tasks into smaller ones, log implementation progress, and update task status.

It gives coding projects a repeatable way to move from an unsolved task to completed work. It also helps keep progress and findings attached to the relevant task or subtask.

dev_workflow — Cursor rule by HexSleeves

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/hexsleeves/tailscale-mcp/dev_workflow

Clone the repo

git clone --depth 1 https://github.com/HexSleeves/tailscale-mcp

Made for: Cursor.

Per session 6,803 This file is loaded in full into every session.

When invoked 6,803 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

Origin 91% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.06803	$0.06803
Opus 5	$0.03402	$0.03402
Sonnet 5	$0.01361	$0.01361
Haiku 4.5	$0.00680	$0.00680

Measured yesterday against content hash 6592b553bc34, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev_workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

91% identical to dev_workflow — 46 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/dev_workflow.mdc · 412 lines

How it starts

The opening of the file, as written. The whole thing — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Taskmaster Development Workflow

This guide outlines the standard process for using Taskmaster to manage software development projects. It is written as a set of instructions for you, the AI agent.

Your Default Stance: For most projects, the user can work directly within the master task context. Your initial actions should operate on this default context unless a clear pattern for multi-context work emerges.
Your Goal: Your role is to elevate the user's workflow by intelligently introducing advanced features like Tagged Task Lists when you detect the appropriate context. Do not force tags on the user; suggest them as a helpful solution to a specific need.

The Basic Loop

The fundamental development cycle you will facilitate is:

list: Show the user what needs to be done.
next: Help the user decide what to work on.
show <id>: Provide details for a specific task.
expand <id>: Break down a complex task into smaller, manageable subtasks.
Implement: The user writes the code and tests.
update-subtask: Log progress and findings on behalf of the user.
set-status: Mark tasks and subtasks as done as work is completed.
Repeat.

All your standard command executions should operate on the user's current task context, which defaults to master.

Standard Development Workflow Process

Simple Workflow (Default Starting Point)

For new projects or when users are getting started, operate within the master tag context:

Start new projects by running initialize_project tool / task-master init or parse_prd / task-master parse-prd --input='<prd-file.txt>' (see taskmaster.mdc) to generate initial tasks.json with tagged structure
Begin coding sessions with get_tasks / task-master list (see taskmaster.mdc) to see current tasks, status, and IDs
Determine the next task to work on using next_task / task-master next (see taskmaster.mdc)
Analyze task complexity with analyze_project_complexity / task-master analyze-complexity --research (see taskmaster.mdc) before breaking down tasks
Review complexity report using complexity_report / task-master complexity-report (see taskmaster.mdc)
Select tasks based on dependencies (all marked 'done'), priority level, and ID order
View specific task details using get_task / task-master show <id> (see taskmaster.mdc) to understand implementation requirements
Break down complex tasks using expand_task / task-master expand --id=<id> --force --research (see taskmaster.mdc) with appropriate flags like --force (to replace existing subtasks) and --research
Implement code following task details, dependencies, and project standards
Mark completed tasks with set_task_status / task-master set-status --id=<id> --status=done (see taskmaster.mdc)
Update dependent tasks when implementation differs from original plan using update / task-master update --from=<id> --prompt="..." or update_task / task-master update-task --id=<id> --prompt="..." (see taskmaster.mdc)

Read the full file on GitHub · 412 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 412 lines · 6,803 tokens per session scan A 6592b553bc34

Subscribe to this mod's changes

dev_workflow is a cursor rule published in the GitHub repository HexSleeves/tailscale-mcp (126 stars, last pushed 2d ago), licensed MIT. It adds 6,803 tokens to every session, about $0.0340 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to dev_workflow, differing in 46 lines, and is treated as a copy.

Code review Planning Productivity mcp mcp-servers tailscale

mintlify

You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.

PrefectHQ/fastmcp · 2,203 tokens

cursor_rules

CogniRepo tool routing rules for {projectname}.

ashlesh-t/cognirepo · 212 tokens

atelier

Atelier UI/UX and Backend Architecture Quality Gate.

anshrajore/atelier-mcp · 534 tokens

cursor_conductor_tasks_workflow

Cursor rule "cursor_conductor_tasks_workflow" from hridaya423/conductor-tasks, covering conductor tasks: comprehensive ai development workflow, primary interaction: mcp server vs. cli, standard development workflow process (ai-driven), task complexity analysis (conceptual) and task breakdown process (using…

hridaya423/conductor-tasks · 0 tokens

cursor_conductor_task_management

description: Best practices for effective task management with Conductor Tasks in an AI-assisted workflow globs: / alwaysApply: true.