What is pm-product-design-brief?

A planning guide for product managers who need to define a product or feature before development begins. It covers the target user, user journey, page structure, interactions, visual direction, responsibilities, and acceptance checks.

Use it before building or upgrading apps, pages, tools, workflows, mobile experiences, PWAs, or product features, especially when several teams or agents will contribute.

It prevents teams from starting implementation with unclear goals, design decisions, or ownership. A written brief gives development, testing, and operations work a shared reference.

pm-product-design-brief — Skill for Claude Code and Codex by joinwell5

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.

Any agent

npx skills add joinwell52-AI/CodeFlowMu-open --skill pm-product-design-brief

Clone the repo

git clone --depth 1 https://github.com/joinwell52-AI/CodeFlowMu-open

Made for: Claude Code, Codex.

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/skills/joinwell52-ai/codeflowmu-open/pm-product-design-brief/github.svg)](https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/pm-product-design-brief)

Your own site

<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/pm-product-design-brief"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/pm-product-design-brief/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/skills/joinwell52-ai/codeflowmu-open/pm-product-design-brief"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/pm-product-design-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 506 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.00067	$0.00506
Opus 5	$0.00034	$0.00253
Sonnet 5	$0.00013	$0.00101
Haiku 4.5	$0.00007	$0.00051

Measured 10d ago against content hash 1a9fbe909893, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

pm-product-design-brief 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 10d 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.

skills/pm-product-design-brief/SKILL.md · 57 lines

How it starts

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

PM Product Design Brief

PM must design the product plan before dispatching implementation work.

When to use

Use this skill for product/application work, especially:

New app, PWA, page, tool, workflow, or feature delivery.
Product merge, product upgrade, mobile/Gateway/PWA enablement.
Requests with unclear product name, user journey, UI direction, acceptance, or role split.

Required behavior

Read the ADMIN task and relevant existing product folders or reports.
Produce a Product Design Brief before broad downstream dispatch.
Include product positioning, target user, scenario, information architecture, key interactions, UI direction, technical/delivery boundary, role split, acceptance criteria, and v2 ideas.
Dispatch DEV / QA / OPS only after the brief is concrete enough to execute.
In the final PM-to-ADMIN report, compare actual delivery against the brief.

UI design ownership

Professional UI design is part of PM's product-planning responsibility in the current team model. PM may use UI playbook personas for information architecture, visual consistency, and usability acceptance, but does not create a new runtime role unless ADMIN explicitly changes the team model.

Output contract

Use the full template in:

docs/skills/pm-playbook/product-design-brief.md

At minimum include:

Product name and one-line positioning
Target user and core scenario
V1 scope and non-scope
Page / region structure
Main user flows
Mobile-first and desktop behavior
UI style direction and state semantics
Data, PWA, offline, Gateway or deployment boundary
DEV / QA / OPS split
Acceptance criteria and evidence plan
V2 upgrade suggestions

Guardrails

Do not copy ADMIN's rough request directly into DEV as the whole task.
Do not dispatch a vague product task without PM-owned design decisions.
Do not claim PWA, Gateway, mobile, or offline support without evidence.
Do not let patrol/ack records replace the final project report.
Do not bypass FCoP task/report lifecycle.

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

10d ago First seen · 57 lines · 67 tokens per session scan A 1a9fbe909893

Subscribe to this mod's changes

pm-product-design-brief is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 16d ago), licensed MIT. It adds 67 tokens to every session and 506 once invoked, about $0.0003 per session on Opus 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.

Design and UX Planning ai-team cursor desktop-app developer-tools human-ai-collaboration mcp

ijfw-ui-spec

Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.

FerroxLabs/ijfw · 83 tokens

ijfw-design

Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.

FerroxLabs/ijfw · 72 tokens

Add Claude design-system and accessibility workflows with UX/UI Agent Skills

Use UX/UI Agent Skills when Claude should generate tokens, component specs, accessibility audits, and framework-specific UI code from a repeatable design workflow.

agentskillexchange/skills · 42 tokens

design-maker

name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens…

zxpmail/ReqForge · 0 tokens

design-brief-builder

name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next…