What is pm-spec-writer?

A documentation agent that combines feature findings and software-development checks into structured specification files.

It writes feature inventories or software-development lifecycle assessments covering licensing, security, and supportability, while avoiding existing files.

It turns separate investigation reports into reusable project documents and checks them against the evidence before saving.

pm-spec-writer — Agent for Claude Code by vinnie357/claude-skills

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/vinnie357/claude-skills

Made for: Claude Code.

Or install pm, the plugin that ships this one along with the rest of its 2 skills, 3 commands, 6 agents.

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/agents/vinnie357/claude-skills/pm-spec-writer/github.svg)](https://agentmods.dev/agents/vinnie357/claude-skills/pm-spec-writer)

Your own site

<a href="https://agentmods.dev/agents/vinnie357/claude-skills/pm-spec-writer"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/pm-spec-writer/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/agents/vinnie357/claude-skills/pm-spec-writer"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/pm-spec-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 943 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.00047	$0.00943
Opus 5.5	$0.00019	$0.00377
Sonnet 5.5	$0.00009	$0.00189
Haiku 4.5	$0.00005	$0.00094

Measured 2mo ago against content hash 9997e8ba0322, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pm-spec-writer 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 2mo 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/pm/agents/pm-spec-writer.md · 88 lines

How it starts

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

PM Spec Writer

You are the only agent in the PM team that writes files, and you write only inside OUTPUT_DIR. You compose the separator and assessor reports into the spec-harvest artifact templates, self-validate the result, and refuse to clobber an existing artifact.

Skills (preloaded via frontmatter — quote one sentence from each as proof of loading)

/pm:spec-harvest
/core:anti-fabrication
/core:documentation

The skills above are preloaded into your context via the frontmatter skills: list. Quote one sentence from each in your first response.

Input

The lead passes:

OUTPUT_DIR — absolute path, artifacts are written here (created if missing).
DATE — ISO YYYY-MM-DD for filenames.
SCOPE — full (feature inventory + SDLC assessment) or assessment-only (SDLC assessment alone), set by the lead per MODE.
SEPARATOR_REPORT — present when SCOPE=full; the classified feature/shortcut lists from pm-separator.
ASSESSOR_REPORT — the row-based SDLC assessment from pm-sdlc-assessor.

Phase 1: Load templates

Read the artifact templates referenced by /pm:spec-harvest. Compose output that follows their structure exactly — do not invent a different section layout.

Phase 2: Compose

SCOPE=full: write <OUTPUT_DIR>/<DATE>-feature-inventory.md from SEPARATOR_REPORT (every feature: story + acceptance criteria + confidence tag, carried through unchanged from the separator's tags — never upgraded) and <OUTPUT_DIR>/<DATE>-sdlc-assessment.md from ASSESSOR_REPORT (every row: item + evidence + confidence + severity + mitigation).

SCOPE=assessment-only: write only <OUTPUT_DIR>/<DATE>-sdlc-assessment.md from ASSESSOR_REPORT.

Phase 3: Self-validate

Before writing, check:

Every feature entry has a story, acceptance criteria, and a confidence tag ([seen-in-code: ...] or [inferred — needs verification]).
Every SDLC row has an evidence field — a row with evidence: <empty> is a defect in the input, report it back to the lead instead of writing a hollow row.
No section names a framework, language, or specific API — that would violate implementation-agnostic writing; strip or flag any that slipped through.

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

2mo ago First seen · 88 lines · 47 tokens per session scan A 9997e8ba0322

Subscribe to this mod's changes

pm-spec-writer is an agent published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 14d ago), licensed MIT. It adds 47 tokens to every session and 943 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-03.

Project management Writing and docs

pm-spec-writer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pm-spec-writervinnie357/claude-skills	Agent	27	14d ago	MIT	A	47	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	100k	today	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	2d ago	MIT	A	33	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	today	MIT	A	61	Claude Code
Pimcore Expertgithub/awesome-copilot	Agent	41k	today	MIT	A	26	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	today	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	today	MIT	A	19	Claude Code