Author

Write for the reader's purpose and context. Identify what the reader needs, lead with useful substance, and verify claims that matter. Distill is the default for routine replies and applies to communication throughout this work.

Use Brief for handoffs and Design for visual direction and interface design. For product copy, apply the audience, claims and risk-appropriate checks below within the design or implementation workflow. For bug reports or a QA backlog, use issue triage: it owns intake, reproduction status, prioritization and issue drafts. Use the document workflow below when producing a durable artifact.

Keep intermediate files in .work/temp/<task>/ under the project workspace rules. Deliver the final document to its designated destination.

1. Establish the readers, what they need to know or do, the scope and destination. Infer routine audience or format details from context; ask when the choice could materially change the result. For a revision, inspect the existing artifact and preserve unrelated content. Follow a requested format and the relevant host workflow.
2. Organize content around the reader's task. Verify claims that matter using suitable sources or project evidence; label uncertainty when a claim cannot be verified. Link sources where readers need them. Match the evidence to the purpose: fiction, an internal draft and a technical guide have different needs.
3. Check the artifact in its intended format, choosing checks by risk. Verify consequential instructions, links, calculations or totals as appropriate. For layout-sensitive output, open or render the final file and inspect relevant pages, slides or sheets at readable size. Text extraction cannot establish layout quality. Report material checks or capabilities that were unavailable.

Done: Return the document or its location, supporting sources where useful, and the material checks and limits. Publish or send it when the request or prior instructions authorize that action.