Installs into .claude/skills of the current project.
Are you the author of Demo Brief?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/wanfeng1028-demo-brief)
---
name: demo-brief
description: Turn a product-demo request into a grounded creative brief with a clear audience, outcome, proof, and scope.
---
# Demo brief
Use this skill when a demo needs a clear purpose before anyone chooses scenes or browser actions. Start from the viewer's job and the product behavior the demo can prove, not from a click list or a preferred video style.
Ask one material question at a time. Offer a small set of concrete choices, mark the evidence-supported recommendation, and retain each answer in the working brief so you do not ask for it again. If the request already answers a question, record it and continue. Never manufacture audience, product facts, or approval.
## Workflow
1. Identify the viewer, their task or decision, the product surface, and the requested outcome.
2. Ground proposed claims in current product evidence: accessible source, tests, documentation, or the running app. Separate known facts from assumptions and open questions.
3. Record required visible proof, non-goals, distribution, accessibility, privacy, and any real time limit. Distinguish required product mechanics from optional navigation. When the demo teaches, state what the viewer can do afterward and the terms the narration must define.
4. Resolve only decisions that materially change the story. Persist the answer, rationale, and relevant evidence reference.
5. Hand a concise approved brief to [demo-storyboard](../demo-storyboard/SKILL.md).
Read [the brief checklist](references/brief-checklist.md) when the request is ambiguous or needs a durable plan file. Do not inspect earlier recordings or action scripts to decide the story; compare them only after the story is locked and only when the user asks for reuse.
