A short command for writing a feature specification or PRD, which is a document describing what to build and why. It focuses on the problem, proposed solution, success measure, and trade-offs.

Use it to draft feature requirements, define one success metric, state what will not be built, and check whether the wording is clear.

It helps turn a vague request into a concise statement of the user problem, intended outcome, and limits of the work.

How MrJoeSack/pm-prompts configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to MrJoeSack/pm-prompts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/MrJoeSack/pm-prompts/main/.claude/commands/spec.md

Clone the repo

git clone --depth 1 https://github.com/MrJoeSack/pm-prompts

Made for: Claude Code.

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/mrjoesack/pm-prompts/spec/github.svg)](https://agentmods.dev/commands/mrjoesack/pm-prompts/spec)

Your own site

<a href="https://agentmods.dev/commands/mrjoesack/pm-prompts/spec"><img src="https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/spec/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/mrjoesack/pm-prompts/spec"><img src="https://agentmods.dev/badge/commands/mrjoesack/pm-prompts/spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 260 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.00008	$0.00260
Opus 5.5	$0.00003	$0.00104
Sonnet 5.5	$0.00002	$0.00052
Haiku 4.5	$0.00001	$0.00026

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

Security

Grade A, and why

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

.claude/commands/spec.md · 39 lines

What it actually says

Feature Spec (Quick)

This is a quick alias for /feature-spec - optimized for rapid specification creation.

Create a feature specification that passes the clarity test:

Structure

Problem Statement (one sentence)
- Users cannot _____ because _____
Solution Overview (one sentence)
- We will build _____ so that _____
Success Metric (one measure)
- Success means _____
Trade-offs (what we won't build)
- We will not build _____ to prioritize this

Input Template

"We need to [build what] because [user problem] so that [outcome]"

Examples:

"We need to simplify onboarding because users abandon the 7-step setup so that more people complete registration"
"We need admin dashboards because enterprise customers can't manage their teams so that we can close more enterprise deals"

Quality Checks

Can you explain this to your grandmother?
Does it pass the McCloskey test? (no fluff, active voice, concrete language)
Are trade-offs explicit?

Output

Provide a clean spec following this structure, then a brief clarity analysis.

Arguments: {{args}}

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 · 39 lines · 8 tokens per session scan A 8ae863dc1e7c

Subscribe to this mod's changes

spec is a command published in the GitHub repository MrJoeSack/pm-prompts (6 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 260 once invoked, about $0.0000 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-08-31.

Planning

spec next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
specMrJoeSack/pm-prompts	Command	6	9mo ago	MIT	A	8	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

pm-prompts: Command for Claude Code