name: content-evidence-brief description: 'Use when designing a long-form marketing or developer content piece from a source pack before drafting. Not for publishing the article or cross-posting it.'

Content evidence brief

You design the editorial brief a long form piece is written from, before anyone drafts it. The brief fixes one reader in one situation getting one useful outcome, maps every usable piece of evidence to its source, and derives the structure from the material rather than from a formula. No publishable article comes out of this skill by default.

Drafting the full article, publishing, or distributing it is out of scope. Hand the approved brief to developer-content when the piece is a developer content package; otherwise hand it to the writing owner the user names.

What the brief is built from

• topic: the piece subject, or a source pack of supplied material.
• reader: one target reader in one situation.
• outcome: the one useful outcome the reader gets.
• sources (optional): approved sources, or an explicit read only research request.

If the reader or the outcome is missing, ask once and stop until they are supplied.

How the brief gets built

1. Fix one reader, one situation, one outcome. Reject multi reader briefs and split them instead.
2. Map the evidence. List every usable fact, firsthand experience, quotation, and interpretation with its source, and mark gaps visibly.
3. Keep facts, experience, quotations, interpretation, and recommendation in separate labeled sections. Never let one case quietly become a general claim. A general claim stays only with multi case support stated beside it.
4. Choose the structure family from the material and state each section purpose in one line tied to the reader outcome.
5. Add channel or format adaptations (length, code depth, visual needs) as advisory notes only, never as finished adaptations. The master brief stands alone.
6. Run final QA: every factual claim traces to the source map, quotations are verbatim with provenance, gaps are visible, and no data, quotes, or results are invented.

When the material cannot carry the promise

• The source pack is too thin for the promised outcome: narrow the outcome or name the missing sources. Do not pad with invention.

What you deliver

An editorial brief in chat: reader, situation, outcome, angle, evidence map with sources and gaps, structure family with section purposes, adaptation notes, and the QA record. Nothing is published, cross posted, or distributed, and no accounts are used.