Files
openprose__prose/packages/std/roles/writer.prose.md
dan f12dcda4d8 Release: the OpenProse Reactor harness (engine + CLI + devtools) — 0.3.0 ideal API surface (#106)
Ships @openprose/reactor 0.3.0, @openprose/reactor-cli 0.2.0, @openprose/reactor-devtools 0.2.0: the Reactor harness (compile-once-intelligent then dumb reconciler, content-addressed receipts, cost scales with surprise) with the distilled ideal public API — curated front door, full @openai/agents passthrough, one typed handle, one Substrate, unified observe, branded ids, and additive forward seams for the fixpoint.
2026-06-02 14:06:56 -07:00

2.2 KiB

name, kind
name kind
writer function

Writer

Produce a written artifact -- a report, email, brief, proposal, code, or any other document -- given requirements and constraints. Use writer when the task is creating new content rather than compressing, extracting, or reformatting existing content. Distinct from summarizer (which compresses) and formatter (which reshapes) -- writer does the creative work.

Description

Produce a written artifact given requirements, audience, and constraints.

Metadata

  • version: 0.1.0

Parameters

  • brief: what to write, including the purpose and key points to cover
  • audience: who will read this and what they need from it
  • format: (optional) structural requirements -- length, sections, tone, style guide

Returns

  • artifact: the written document. Every claim in the returned artifact is specific rather than vague ("revenue grew 40% YoY" not "revenue grew significantly"); its structure follows the format requirements if provided, or uses a sensible default structure; its content addresses the audience's needs and knowledge level; and it contains no filler -- every sentence earns its place.

Errors

  • insufficient-brief: the brief does not contain enough information to produce a meaningful artifact
  • contradictory-requirements: the format or audience constraints conflict with each other (e.g., "write a 100-word comprehensive technical analysis")

Strategies

  • when the brief is rich: organize around the strongest points first, not the order they appear in the brief
  • when the audience is non-technical: lead with implications and actions, put methodology and details in appendices or later sections
  • when length is constrained: cut redundancy and background before cutting substance
  • when tone is unspecified: match the formality of the brief and the expectations of the audience

Notes

Writer creates new content. Summarizer compresses existing content. Formatter reshapes structured data into a presentation format. Researcher gathers information. In a typical pipeline, researcher finds the data, writer turns it into a document, and formatter handles the final presentation. Writer is the role that synthesizes, argues, explains, and persuades.