Set up
Try a plugin
The Design plugin ships with /design-handoff and other research and structuring skills as a starting point, already shaped to the section order most design reviews expect. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.
/design-handoffGenerate developer handoff specs from a design./research-synthesisSynthesize user research into themes, insights, and recommendations.Connect your tools
Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access(opens in new tab).
Add a connector(opens in new tab) for each tool you want Claude to use.
Set your working folder
Drag the files you'll use (exported Slack threads, meeting notes, the screenshots people kept pasting) into one folder on your machine, then point Claude at it. Claude reads from it and writes the assembled spec back to it. If you write specs regularly, create a project(opens in new tab) from that folder so your spec template, instructions, and memory stay attached.
The prompt
Copy this into Claude
Assemble everything in this folder into a single design spec. Structure it as problem, goals, constraints, proposed solution, open questions, and out of scope. Quote the source for any decision already made and flag anything contradictory.
Why this works
Name the section order. The output matches the review template, no reshuffling.
Ask it to cite its sources. Nobody re-litigates what was already settled in Slack.
Flag contradictions explicitly. Conflicts surface before the review, not during it.
Put all the context in one place. Threads, notes, and screenshots all carry equal weight.
Get a better draft
Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.
Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.
Make Claude work for you
A plugin skill is a starting point. Customize it with your own practices and expertise, or save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.
Make what we've done in this task so far into a skill, or edit the /design-handoff skill with my feedback.
Make it repeatable
Share it as an artifact
A spec is out of date the moment someone replies in the channel. Ask Claude to publish it as an artifact and the cross-functional team has one link — re-run the skill or schedule it to refresh.
Publish that spec as an artifact for the squad. Keep a "decisions changed since last version" section at the top.
Run it the morning before every review
Review is on the calendar, the spec should already reflect last night's thread. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and set the customized skill to run each morning, re-reading the channel and folder.
Set up a scheduled task for weekdays at 8am: re-read #checkout-redesign and Design/Checkout-Redesign and re-run /design-handoff, updating the spec file and listing any decisions that changed overnight.
Each weekday at 8am, re-reads the project channel and folder, re-runs /design-handoff, and updates the spec with a list of decisions that changed overnight.
Share with your teammates
Your customized /design-handoff now carries your section order, your decision-log format, and your contradiction flags. Share it so every designer on the team writes specs the same way, and reviewers know exactly where to look no matter who owns the project.