design-brief-writerlisted

Design requests rarely arrive as briefs. They arrive as a Slack thread with four opinions, an email that forwards an older email, and a ticket whose title is the only sentence anyone agreed on. This skill reads whatever you paste and writes the brief the request should have come with. Every line is tagged: STATED when the source says it (with the quote), INFERRED when the skill reads it between the lines (with the reason), OPEN when nobody has said it yet. It needs only pasted text, so it runs the same on claude.ai, in Claude Code, and in Claude Cowork. Anthropic's [design plugin](/guides/design/claude-design-plugin-guide) covers research synthesis, critique, and handoff, but ships no brief skill; this is the step before those. ## When to use this skill - A request came in through chat or email and you want one page you can send back with "is this what you meant?". - Several stakeholders have said different things and the differences need to be visible before you open Figma. - A ticket has a title and a screenshot and nothing else, and you need the questions list to go get answers. - You are kicking off with a contractor or a new teammate and the brief has to stand on its own. > [!NOTE] > The brief contains only what the source supports. The skill does not add constraints from general practice ("must meet WCAG", "mobile first") unless the source says so; it lists them as questions instead. It never invents a deadline: dates come from the source or stay as placeholders. If