What problem does it solve? Multi-agent content setups produce generic, duplicated, or unsourced posts because every role shares one vague instruction and handoffs happen in conversation. This Skill replaces that with a written pipeline: six roles with explicit contracts, one inspectable campaign record that travels between them, and a distribution stage that gives every asset its own argument instead of a shortened draft. ## Core Features & Use Cases - Six role contracts: Signal scout, researcher, strategist, writer, distribution, and editor each own one decision with written owns/reads/returns/must-not/done-when clauses and checkable thresholds. - Campaign record: One Markdown file per campaign at .agents/newsroom/<slug>.md carries decisions and evidence between roles, sessions, and restarts, with per-stage completion rules and a return-to-sender halt format. - Argument-based distribution: Seven entryways (proof, mechanism, workflow, risk, result, critique, compression), a 0-3 standalone scoring check, and a claim/opening/entryway collision gate prevent a week of posts repeating one argument. - Founder-led mode: An intake contract and account lanes for turning weekly founder interviews or voice notes into distinct personal and company content while keeping publishing human-approved. - Use Case: A founder supplies a 20-minute weekly voice note; the pipeline extracts verified claims, picks one angle, and returns an approval-ready founder post and company proof post that argue different things from the same evidence packet. ## Quick Start Use suede-newsroom to move this idea through the pipeline: scout, research, angle, flagship, then a distribution set where every asset carries its own entryway and passes the collision gate, stopping at the human approval boundary.
