What "brief" actually means, across the disciplines that use it as jargon.
A brief is a short, structured document that fixes an objective, audience, and constraints before execution begins -- so the executor (a legal associate reading a case brief, a creative team reading a campaign brief, or an AI agent reading a task brief) doesn't have to guess. Three genuinely different disciplines converge on that same underlying shape: legal case briefs (IRAC structure), marketing/advertising creative briefs, and Anthropic's own documented prompt-engineering guidance for briefing Claude on a task. This site records that convergence as a durable, sourced catalog -- every row cites a real URL or a real file in this repository, never an assumed convention.
Legal, marketing, and prompt-engineering conventions for "brief" are catalogued side by side -- each with its own real structural convention, not a single invented template forced onto all three.
This repo has no legal-coworker skill and no campaign-brief skill. Searched for both this session; neither exists. The catalog says so rather than inventing content to fill the gap.
Every row's source_doc is a URL fetched this session or a repo-relative file path that was actually read.
Live catalog
4 rows, seeded from real research into this Worker's own D1 database (brief_types). Browse → or hit the JSON API.