open-press Writing

open-press writing owns the reader-facing document argument — what the document says, in what order, with which heading structure, and what facts need confirmation. It is also the entry point for portable writing skills (tone, language, genre, teaching).

Responsibilities

• Define audience, purpose, narrative flow, and section order.
• Decide H1/H2/H3/H4 structure, formal TOC depth, reader outline depth, and appendix placement (see Hierarchy below).
• Rewrite prose, tables, captions, and content transitions.
• Own the <TableCaption>...</TableCaption> placement rule (single authoritative definition; starter-bearing skills link to this skill, not redefine it).
• Decide when prose should become a table, figure, chart, or callout — and equally when not to reach for a component, so MDX building blocks stay reading aids instead of imitations of interactive UI (see Components are reading aids, not interactive UI below).
• Preserve confirmed facts and mark missing facts explicitly.
• Load portable writing skills based on content type (see triggers below).
• Reference openpress for system operations, source/generated boundaries, and verification commands instead of defining them here.

Boundaries