What is taskmaster_flow?

A set of instructions for managing development work with Taskmaster, a task-tracking workflow. It defines a loop for listing tasks, choosing the next one, viewing details, breaking work into subtasks, and recording progress.

Use it to list and inspect tasks, expand large tasks into smaller ones, update subtask progress, and mark completed work as done.

It gives an agent a consistent way to organize complex work and keep task status up to date. This makes unfinished work and completed steps easier to see.

taskmaster_flow — Cursor rule by compozy

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/compozy/gograph/taskmaster_flow

Clone the repo

git clone --depth 1 https://github.com/compozy/gograph

Made for: Cursor.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 6,791 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 92% 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.00007	$0.06791
Opus 5	$0.00003	$0.03395
Sonnet 5	$0.00001	$0.01358
Haiku 4.5	$0.00001	$0.00679

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

Security

Grade A, and why

taskmaster_flow 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

92% identical to dev_workflow — 65 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/taskmaster_flow.mdc · 413 lines

How it starts

The opening of the file, as written. The whole thing — 413 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 · 413 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 · 413 lines · 7 tokens per session scan A d4350bac9240

Subscribe to this mod's changes

taskmaster_flow is a cursor rule published in the GitHub repository compozy/gograph (9 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 6,791 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to dev_workflow, differing in 65 lines, and is treated as a copy.

Planning Productivity

taskmaster_flow

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Taskmaster Development Workflow

The Basic Loop

Standard Development Workflow Process

Simple Workflow (Default Starting Point)

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

typescript

coolify-ai-docs

python_lib

specs