A command that selects the next open project-management task and marks it as in progress, unless used in preview mode. It reads the project's task and configuration files and shows the task's evidence and suggested action.

Claiming the highest-priority available governance task, previewing that choice with --peek, and finding the evidence or follow-up command needed to complete it.

It removes the need to decide manually which unfinished task should be taken next. It also keeps the task status and its mirrored project records aligned.

next — Command by wei63w

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 commands/wei63w/pm-manager/next

Clone the repo

git clone --depth 1 https://github.com/wei63w/pm-manager

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

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

Security scan A 0 findings. Scan, not verified.

Origin 100% 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.00011	$0.00510
Opus 5	$0.00005	$0.00255
Sonnet 5	$0.00002	$0.00102
Haiku 4.5	$0.00001	$0.00051

Measured 2d ago against content hash 50de1ed9008c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

next 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 2d 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.

Origin

This is a copy

100% identical to pm-next — 0 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.

skills/pm-manager/templates/commands/next.md · 40 lines

What it actually says

User Input

$ARGUMENTS

Optional: --peek (do not mark in_progress).

Outline

Require init. Read state/todo.md.
Pick the first open/in_progress item ordered by blocking>high, then P0>P1 (no 3-item cap).
Unless --peek, set status in_progress in state + module mirror.
Print task, evidence link, suggested action; remind /pm-done TODO-id.

Shared Workflow (all /pm-* commands)

Follow this order when the command mutates .pm/ state:

Read .pm/config/project.yaml and .pm/config/local.yaml (if missing and command is not init → recommend /pm-init).
If .pm/ metadata is valid, load it; do not force a full-repo rescan. On-demand incremental scan using sources + extra_scan_roots + --path + conversation paste (highest priority for /pm-fix). Prefer .pm/architecture/map.json and the document index before walking the tree.
Desensitize evidence → .pm/evidence/scans/{command}-{timestamp}.json (secrets → ***). Never persist raw secrets.
Optional charter compare only when charter.status == approved (attach confidence). Draft PRD/charter MUST NOT be used as the baseline.
Incremental merge into module findings.md / todo.md; sync authoritative state/todo.md.
Refresh state/overview.md with all open/in_progress blocking+high todos (no 3-item cap). Medium/low: counts only unless --verbose.
Append audit to .pm/state/audit.jsonl (command, time, input/output summary; include reasoning when the step was AI-produced).
Output risk summary + recommended next step (≤20 lines). Never auto-write source/SQL/cloud or land generated docs/rules without explicit user confirmation.
Closing: templates/commands/_closing.md 轻量档。中文摘要。

Design baseline: docs/prd.md + 宪章。

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.

2d ago First seen · 40 lines · 11 tokens per session scan A 50de1ed9008c

Subscribe to this mod's changes

next is a command published in the GitHub repository wei63w/pm-manager (96 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 510 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pm-next, differing in 0 lines, and is treated as a copy.

Planning Productivity Project Management Project management agent-skills ai-agents claude-code cursor skills

next

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

What it actually says

User Input

Outline

Shared Workflow (all /pm-* commands)

What this file has done since we first saw it

Other commands, from other repositories

webperf

spec

project

install

audit-rules

search