planning-queue

A set of writing rules for the project’s working queue, a list of planned work ordered by priority and dependencies.

In plain words
What is it for?
Editing docs/queue.md, adding queued work, reprioritising items, and keeping queue links consistent.
Why use it?
It keeps the queue aligned with the backlog and story files, so planned work does not point to missing documents or use stale ordering.

Cursor rule for Cursor

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/alexpialetski/doccraft/planning-queue
Clone the repo
git clone --depth 1 https://github.com/alexpialetski/doccraft

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 253 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00253
Opus 5 $0.00000 $0.00127
Sonnet 5 $0.00000 $0.00051
Haiku 4.5 $0.00000 $0.00025

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

Security

Grade A, and why

planning-queue 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.

.cursor/rules/planning-queue.mdc · 25 lines

What it actually says

Managed by doccraftdoccraft update regenerates this file. Local edits will be overwritten. See doccraft.json to override project-specific vocabulary and paths without touching this file.

Working queue

When editing docs/queue.md:

  • The editorial process (ordering rules, dependency precedence, parallel waves) lives in the doccraft-queue-audit skill. Follow that skill rather than reinventing.
  • Keep the Suggested order table in sync with story urgency / impact when you reprioritise. docs/backlog.md owns the full P-tier tables and Status column.
  • Rows must link to existing files under docs/stories/; add a story file (and a row in the backlog's Story files table) when introducing a new queued item.
  • After any depends_on edit or meaningful queue reorder, invoke doccraft-queue-audit in the same turn to keep the graph and tables consistent.
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. yesterday First seen · 25 lines · 0 tokens per session scan A f25bf165f643

Subscribe to this mod's changes

planning-queue is a cursor rule published in the GitHub repository alexpialetski/doccraft (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 253 tokens. 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-08-31.

Related

Other cursor rules, from other repositories

archgate-governance

Archgate ADR governance — enforces architecture decision records.

archgate/cli · 195 tokens

test-estimation

Estimate testing effort, duration, and resourcing for a Katalon True Platform/TestOps cycle. Use when the question is how long testing will take, how many testers it needs, whether the scope fits the sprint window, or what a scope change costs in person-hours. Sizes design, manual execution, automated execution and…

katalon-labs/true-skills · 194 tokens

release-analyze

Analyze Katalon True Platform/TestOps release readiness from testing quality data. Use when you need to use Katalon MCP metrics and results to assess whether a release, sprint, iteration, version, test plan, suite, or repository is ready to ship; summarize requirement coverage, execution health, defect risk, test…

katalon-labs/true-skills · 107 tokens

test-plan

Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…

katalon-labs/true-skills · 137 tokens

fcp-pm-role

Cursor rule "fcp-pm-role" from joinwell52-AI/FCoP, covering fcp pm 角色规则, 接收来源, 核心职责, 派发任务命名规范 and 优先级标记.

joinwell52-AI/FCoP · 355 tokens

task-viewer

Use when the user wants to open, launch, start, or view the Claude Code task dashboard / Kanban board — a live web UI showing tasks across sessions (pending / in-progress / completed), dependencies, timeline, and activity. Wraps the standalone claude-task-viewer Express app. Not for creating or editing tasks (Claude…

Surya8991/AgentMaster · 76 tokens