A project-outline command for new or empty projects. It turns a user's intent into planning documents such as goals, features, milestones, and a draft project charter.

Use it to define project scope, users, features, exclusions, technology preferences, timing, work process, and initial milestones.

It records what the project should achieve before application code is written, while keeping the plan separate from approved requirements.

outline — 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/outline

Clone the repo

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

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

When invoked 593 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.00015	$0.00593
Opus 5	$0.00008	$0.00296
Sonnet 5	$0.00003	$0.00119
Haiku 4.5	$0.00002	$0.00059

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

Security

Grade A, and why

outline 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.

Origin

This is a copy

100% identical to pm-outline — 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/outline.md · 43 lines

What it actually says

User Input

$ARGUMENTS

Outline

Require init. Collect intent: goal, users, features, non-goals, stack prefs, timeline, process.mode.
Write .pm/outline/project-outline.md, epics.md, milestones.md.
Sync draft .pm/charter/* (REQ-xxx); set outline/charter status draft, source generated.
Do not write application source code.
Do not treat the outline/charter as acceptance criteria until /pm-charter approve (or /pm-init confirm for PRD).
Recommend /pm-init confirm or /pm-charter 向导；技术扫描用 /pm-all（不必先 approve）。

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: _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.

3d ago First seen · 43 lines · 15 tokens per session scan A 16ca6bea2ccf

Subscribe to this mod's changes

outline is a command published in the GitHub repository wei63w/pm-manager (96 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 593 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-outline, differing in 0 lines, and is treated as a copy.

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

outline

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

install

audit-rules

search

index