Slash Command

Write Brief

Guide the user through creating a clear, actionable product brief

Type: Slash Command
Repository: jeremylongshore/tons-of-skills-marketplace
GitHub stars: 2.8k
License: MIT
Repo last updated: Sep 27, 2026
Source file: plugins/productivity/pm-ai-partner/commands/pm/write-brief.md

What Write Brief is

Write Brief is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Write Brief gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Write Brief

Claude Code

Download write-brief.md from the repository.
Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
Run it by typing / followed by its name.

Claude Cowork

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
In Customize → Skills, click +, then upload the ZIP.
Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/productivity/pm-ai-partner/commands/pm/write-brief.md, shared under the repository's MIT license. Read the full file on GitHub.

Help me write a product brief for: $ARGUMENTS

Instructions

Guide me through creating a clear, actionable product brief that engineering can use to scope and build. Follow this process:

Gather context — Ask me clarifying questions about the problem, users, constraints, and goals. Don't start writing until you understand the situation.
Propose structure — Show me an outline before drafting.
Draft — Write the full brief.
Review — Highlight gaps and suggest improvements.

Brief Structure

# [Feature Name]

## Problem Statement
What problem are we solving? Who has this problem? Why now?

## Proposed Solution
What are we building? (High-level — leave "how" to engineering)

## User Value
Why will users care? What's the measurable benefit?

## Success Metrics
| Metric | Current | Target |
|--------|---------|--------|

## Scope
### In Scope (v1)
### Out of Scope (and why)
…

Quality Checklist

Before finalizing, verify:

Problem is specific (not "improve engagement")
Solution describes "what" not "how"
Metrics are measurable with current instrumentation
Scope has explicit exclusions
Open questions are honest about unknowns
A senior engineer could read this and start scoping

Save the brief to sandbox/planning/ as a draft. When ready to share, move to product-catalog/planning/.

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Write Brief?

Write Brief is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Guide the user through creating a clear, actionable product brief

How do I install Write Brief in Claude Code?

Download write-brief.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Write Brief in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Write Brief safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.