agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/pm-product-design-brief/SKILL.md

pm-product-design-brief

Skill2 starsChanged 4 months agoMITView on GitHub

Create a PM-owned product design brief before dispatching product, UI, PWA, mobile, Gateway, app merge, or feature upgrade work. Use when PM must define positioning, user value, information architecture, interaction, visual direction, acceptance, and multi-agent split before DEV/QA/OPS execution.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for product/application work, especially:

    line 12
  2. Distinctive:

    Read the ADMIN task and relevant existing product folders or reports.

    line 20
  3. Distinctive:

    Use the full template in:

    line 32
  4. Distinctive:

    Do not copy ADMIN's rough request directly into DEV as the whole task.

    line 52
  5. Distinctive:

    Do not dispatch a vague product task without PM-owned design decisions.

    line 53
  6. Distinctive:

    Do not claim PWA, Gateway, mobile, or offline support without evidence.

    line 54
  7. Distinctive:

    Do not let patrol/ack records replace the final project report.

    line 55
  8. Distinctive:

    Do not bypass FCoP task/report lifecycle.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read the ADMIN task and relevant existing product folders or reports.
  2. Produce a Product Design Brief before broad downstream dispatch.
  3. Include product positioning, target user, scenario, information architecture, key interactions, UI direction, technical/delivery boundary, role split, acceptance criteria, and v2 ideas.
  4. Dispatch DEV / QA / OPS only after the brief is concrete enough to execute.
  5. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free