design-handoff-brief
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.
npx skills add mohitagw15856/pm-claude-skills --skill design-handoff-brief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 Ask the user for these if not provided: - **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 2. Extract user goal (reframe from feature language to user outcome language) 3. Identify constraints — technical limitations, brand guidelines, accessibility requirements 4. List edge cases the design must handle 5. Define success criteria the design should be evaluated against 6. Write a "not in scope"
- Required Inputs
- What Designers Actually Need (and PMs Often Skip)
- Process
- Output Structure
- Design Brief: [Feature Name]
- Quality Checks
- Anti-Patterns
What does the design-handoff-brief skill do?
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.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill design-handoff-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.