dev_workflow

dev_workflow is a cursor rule for Cursor from neuromechanist/research-skills. It costs 1,074 tokens per session, scanned A, original, BSD-3-Clause.

A development workflow for breaking complex projects into tracked tasks, recording research and decisions, and managing dependencies with Taskmaster.

In plain words
What is it for?
Use it to parse requirements, create and expand tasks, find the next piece of work, log progress, and check task relationships.
Why use it?
It turns broad project requirements into smaller pieces and keeps progress, technical findings, failed attempts, and dependencies visible.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it to parse requirements, create and expand tasks, find the next piece of work, log progress, and check task relationships.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/neuromechanist/research-skills/dev_workflow
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.

Clone the repo
git clone --depth 1 https://github.com/neuromechanist/research-skills

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for dev_workflow

README.md
[![agentmods](https://agentmods.dev/badge/rules/neuromechanist/research-skills/dev_workflow.svg)](https://agentmods.dev/rules/neuromechanist/research-skills/dev_workflow)
Your own site
<a href="https://agentmods.dev/rules/neuromechanist/research-skills/dev_workflow"><img src="https://agentmods.dev/badge/rules/neuromechanist/research-skills/dev_workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,074 This file is loaded in full into every session.
When invoked 1,074 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01074 $0.01074
Opus 5 $0.00537 $0.00537
Sonnet 5 $0.00215 $0.00215
Haiku 4.5 $0.00107 $0.00107

Measured 3d ago against content hash f8499b4ec5e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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 3d ago.

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.

plugins/project/templates/cursor/planning/advanced-taskmaster/dev_workflow.mdc · 148 lines

How it starts

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

TaskMaster Development Workflow for {{PROJECT_NAME}}

Documentation-Driven Development

Core Documents

  • TaskMaster DB: Primary task tracking (.taskmaster/)
  • .context/research.md: Solution exploration and technical references
  • .context/ideas.md: Abstract concepts and design exploration
  • .context/scratch_history.md: Failed approaches and lessons learned

Document Integration

  • TaskMaster handles task management
  • Use .context/research.md for technical exploration
  • Document design decisions in .context/ideas.md
  • Track failures in .context/scratch_history.md

Task Management: AI-Powered

Setup

task-master init --yes
task-master parse-prd scripts/prd.txt --num-tasks=15 --research

MCP Tools (Recommended)

  • get_tasks, next_task, get_task - Task viewing
  • update_subtask, update_task - Progress logging
  • add_task, expand_task - Task creation/breakdown
  • add_dependency, validate_dependencies - Dependencies

CLI Fallback

task-master list              # View tasks
task-master next              # Find next task
task-master show <id>         # Task details
task-master set-status <id> --status=in-progress|done

Daily Workflow

  1. Find next task: next_task / task-master next
  2. Review context: Check .context/ideas.md and .context/research.md if needed
  3. Start work: Set status to in-progress
  4. Research if blocked: Update .context/research.md with findings
  5. Create branch: git checkout -b "feature/short-description"
  6. Implement: Code following task requirements
  7. Log progress: update_subtask --prompt="implementation notes"
  8. Test & commit: Concise message <50 chars, no emojis
  9. Mark complete: Set status to done
  10. Update docs: Document learnings in .context/ files
  11. Create PR: Descriptive title, reference task in body

Task Breakdown & Dependencies

Complex Tasks

# MCP: expand_task(id="5", num="4", research=true)
task-master expand <id> --num=4 --research

Read the full file on GitHub · 148 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.

  1. 3d ago First seen · 148 lines · 1,074 tokens per session scan A f8499b4ec5e5

Subscribe to this mod's changes

dev_workflow is a cursor rule published in the GitHub repository neuromechanist/research-skills (45 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 1,074 tokens to every session, about $0.0054 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.