design-handoff-brief SKILL.md skillA
design-handoff-brief from mohitagw15856/pm-claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mohitagw15856/pm-claude-skills/design-handoff-brief@git:20261011.d31ce81Pins git:20261011.d31ce81 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mohitagw15856/pm-claude-skills
- Path
plugins/pm-advanced/skills/design-handoff-brief/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261011.d31ce81, committed Oct 11, 2026
- First version recorded
- Apr 20, 2026
- Size
- 5,473 bytes
- Repository stars
- 1,475
- License
- MIT
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Design Handoff Brief Skill Produce a design brief that sets designers up for success — grounding them in user context and constraints before they open Figma, not after they've gone in the wrong direction. ## Required Inputs Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked *(assumed, confirm)* and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about). - **Feature brief or PRD** (even rough notes work) - **Designer's name or team** (for personalisation) - **Technical constraints** (any engineering limitations already known) - **Timeline** (when does design need to be done?) ## What Designers Actually Need (and PMs Often Skip) - The user's goal, not the feature name - The emotional state of the user at this moment in the journey - What success looks like — how will we know the design worked? - Constraints: technical, legal, brand, accessibility - Edge cases that must be handled - What we're explicitly NOT solving for ## Process 1. Read the feature brief or PRD provided …
Read the whole file at its exact version.
How to install
mdr add mohitagw15856/pm-claude-skills/design-handoff-brief@sha256:83c9a86f5e427bb5The line at the top of this page pins the label git:20261011.d31ce81, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jgwydavnu7nxf5hm)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 20, 2026 and Oct 11, 2026, about one every 43 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.d31ce81 latest | 2026-10-11 | d31ce81 | 5,473 B | A | view · diff |
| git:20261006.b9ea321 | 2026-10-06 | b9ea321 | 5,214 B | A | view · diff |
| git:20260816.aad1af1 | 2026-08-16 | aad1af1 | 5,045 B | A | view · diff |
| git:20260608.affae03 | 2026-06-08 | affae03 | 3,931 B | A | view · diff |
| git:20260420.513e1d3 | 2026-04-20 | 513e1d3 | 3,136 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5473 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
mohitagw15856/pm-claude-skills · 1,475 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jgwydavnu7nxf5hm GET https://markdownregistry.com/api/v1/resolve?ref=mohitagw15856/pm-claude-skills/design-handoff-brief GET https://markdownregistry.com/api/v1/blob/83c9a86f5e427bb5ae84f1b4fb996adfe5aae4a69f092f8ed86d5b462ae025a1
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.