Brief types
Every real "brief" convention this site is grounded in, filterable by discipline:
This repo's own brief-adjacent skill: brand-voice
This repository has no dedicated legal-coworker skill and no campaign-brief skill under plugins/cwc-product-management (verified by search this session: cwc-product-management ships exactly one skill, brand-voice). The closest in-repo artifact to a "brief" convention is that skill's own discipline — source a real quoted example before drafting any guideline, present the draft for human confirmation, and record only a sourced, gated write — the same source-before-draft discipline every other row in this table describes for its own discipline.
Source: plugins/cwc-product-management/skills/brand-voice/SKILL.md
Legal case brief (IRAC)
A concise summary and analysis of a court opinion, prepared for classroom discussion or practice, that establishes the parties, the issue, the rule, and the outcome before any argument is built on top of it.
Source: https://pressbooks.uwf.edu/healthcarelaw/part/irac-analysis/
Creative / marketing campaign brief
A short planning document an account team hands to a creative team before production begins, fixing the objective, audience, and deliverables so creative work has a measurable target rather than an open-ended brainstorm.
Source: https://asana.com/resources/how-write-creative-brief-examples-template
Briefing Claude on a task (prompt engineering)
Anthropic's own prompting guidance converges on the same shape as the legal and marketing brief conventions above, applied to instructing Claude: state the task explicitly, name who the output is for, and define what "done" looks like before generation starts.
Source: https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/claude-prompting-best-practices
Machine-readable version: GET /api/briefs