A draft-promotion command that moves a product document into a Beads issue, a tracked work item, after a required review passes. It can file strategy, product requirements, or launch documents under the matching approval gate.

Use it to promote a reviewed strategy, PRD, specification, or launch plan into the appropriate gate-ready issue.

It prevents unreviewed drafts from being treated as ready for approval. It also provides a consistent path from a working document to a tracked project item.

pm-promote — Command for Claude Code by VandanaAjayDubey111/great-pm

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/VandanaAjayDubey111/great-pm

Made for: Claude Code.

Or install great-pm, the plugin that ships this one along with the rest of its 114 skills, 34 commands, 48 agents, 5 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-promote/github.svg)](https://agentmods.dev/commands/vandanaajaydubey111/great-pm/pm-promote)

Your own site

<a href="https://agentmods.dev/commands/vandanaajaydubey111/great-pm/pm-promote"><img src="https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-promote/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/vandanaajaydubey111/great-pm/pm-promote"><img src="https://agentmods.dev/badge/commands/vandanaajaydubey111/great-pm/pm-promote.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.01069
Opus 5.5	$0.00016	$0.00428
Sonnet 5.5	$0.00008	$0.00214
Haiku 4.5	$0.00004	$0.00107

Measured 27d ago against content hash 670fded591be, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pm-promote 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 27d 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.

commands/pm-promote.md · 94 lines

How it starts

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

You are the great-pm /pm-promote command. Move a draft from .great-pm/drafts/ into a gate-ready Beads issue, but only after pm-reviewer clears it.

Parse arguments

<draft-path> (required) → path to the draft (e.g. .great-pm/drafts/strategy-acme-q3.md).
--gate= (optional) → which gate to file under. If omitted, infer from the draft's filename prefix: strategy-* → gate:strategy, prd-* / spec-* → gate:spec, launch-* / gtm-* → gate:launch.

Pre-flight

echo "cwd=$(pwd)"
DRAFT="${1:?usage: /pm-promote <draft-path> [--gate=...]}"
[ -f "$DRAFT" ] && echo "DRAFT_OK" || echo "NO_DRAFT"
ls .great-pm/PROJECT.md 2>/dev/null && echo "PROJECT_OK" || echo "NO_PROJECT"

If NO_DRAFT → BLOCKED. Tell the user the path doesn't exist. If NO_PROJECT → BLOCKED. Tell the user to bootstrap PROJECT.md first.

Operating procedure

Step 0 — refine the user's query (transparent Mode B). Invoke query-refiner-pm with $ARGUMENTS. The refiner returns:
```
You typed:  <original>

Refined to: <refined brief>

What changed: <one line>

Proceeding with refined. Reply "use original" to override.
```
Use the refined version as the brief for subsequent steps UNLESS the user replies "use original". Log the refinement to .great-pm/refinements/$(date +%Y-%m-%d).log. This wiring is universal across great-pm commands per the gate-policy: explicit discipline — you make the user's leverage visible while preserving their ability to override.
Read the draft. Confirm it has the required structural sections for the target gate (e.g. spec drafts must have Problem / Users / Solution / Metrics / DoD).
Mandatory pm-reviewer pass — spawn pm-reviewer with the draft and the target gate. Wait for verdict. The verdict travels unedited to the user.
If verdict is PASS:
- Create Beads issue: bd create --title="gate:<strategy|spec|launch> — <draft-title>" --description="See $DRAFT" --type=task --priority=1.
- Label it: bd update <id> --labels=gate,gate:<strategy|spec|launch>.
- Append verdict log to .great-pm/verdicts/<draft-slug>-<YYYY-MM-DD>.log.
- Update .great-pm/PROJECT.md initiative to reflect the gate now open.
- DO NOT close the gate yourself. Under gate-policy: explicit (great-pm's default), gates are closed ONLY by the human running /pm-gate approve <id>. You FILE the gate; the human DECIDES.
- Report the Beads ID and the exact command for the human to run:
```
Filed gate:<gate> as bd <id>.
To advance the pipeline, run:  /pm-gate approve <id>
To reject with reason,  run:   /pm-gate reject <id> "<reason>"
```

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

27d ago First seen · 94 lines · 39 tokens per session scan A 670fded591be

Subscribe to this mod's changes

pm-promote is a command published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 27d ago), licensed MIT. It adds 39 tokens to every session and 1,069 once invoked, about $0.0002 per session on Opus 5.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-21.

LLM Multi-Agent Planning Project management agentic ai-agents claude-code-plugin

pm-promote

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Parse arguments

Pre-flight

Operating procedure

What this file has done since we first saw it

Other commands, from other repositories

poc

rfc

exception

new-track

conductor-new-track

dashboard