Skip to main content

write-a-creative-brief

Translate a creative request into an aligned brief covering audience, outcome, message, constraints, deliverables, and approval. Use when commissioning design, copy, photo, video, or campaign work.

소스 정보

저장소
protosphinx/sphinxstack
최근 소스 활동
2026년 7월 29일 13:55
감지된 SKILL.md 언어
영어
스타
3
포크
0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기
2 개 파일

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
write-a-creative-brief
category
design
description
Translate a creative request into an aligned brief covering audience, outcome, message, constraints, deliverables, and approval. Use when commissioning design, copy, photo, video, or campaign work.
# write-a-creative-brief Define the problem and boundaries without prescribing a decorative solution before exploration. ## Procedure 1. Identify the decision owner, stakeholders, creator, users, deadline, budget, and approval path. 2. State the business or communication problem and the observable outcome the work should influence. 3. Define the primary audience using evidence, context, need, and current behavior. 4. Write the single most important message and supporting points. 5. Inventory deliverables, channels, sizes, formats, languages, accessibility, usage rights, and production constraints. 6. Gather mandatory content, brand rules, legal or policy review, existing assets, and references with an explanation of what each demonstrates. 7. Separate fixed requirements from preferences and open creative territory. 8. Define milestones, feedback rounds, named approvers, evaluation criteria, and change-control rules. 9. Review the brief with the creator and resolve contradictions before work begins. ## Failure plan - Do not disguise stakeholder taste as audience evidence. - Never include assets, likenesses, music, fonts, or claims without appropriate rights and review. - If objectives conflict, obtain a decision rather than asking the creator to reconcile them silently. - Reject vague success criteria such as “make it pop” unless translated into an observable need. ## Done - Audience, outcome, message, deliverables, constraints, rights, and approvals are recorded - Fixed requirements and creative choices are distinguishable - Creator and decision owner confirm the brief is feasible and testable
GitHub에서 보기