technical-report-writing
Technical Report Writing
Work and baseline
Write for a reader who lacks the drafting conversation, and select and organize information before polishing sentences. Infer reader, task, sources, language, and medium from context, and ask only about gaps that change meaning or authority. A new document returns the artifact, a review returns findings and edits nothing, and a revision changes only what was authorized. In a user-edited copy, the current copy is the baseline; compare it with the closest earlier version to see which functions the user removed and kept. Only the user's edits show preference, so isolate changes other agents made. Preserve established terms, templates, and voice, and change the system itself only when authorized. The Korean clarity floor in Korean writing also covers ordinary Korean answers and progress reports.
Meaning and scope of change
A correction that names a type ("drop sentences like this") covers every instance; one that names a sentence covers that sentence, and other instances are reported, not edited. All else stays byte-identical, including approved examples, mechanism, equations, figures, and any block, bullet, or page note the user wrote; a page note is an instruction, never reader text. After editing, diff against the previous version and confirm nothing outside the correction moved. A correction removes a function, so re-creating it elsewhere repeats the defect, as when a deleted reading guide returns as toggle titles. Instructions shape the document without becoming its text ("newest first" becomes an ordering), and reviewer, subagent, and self-check notes stay out of it.
To explain a thing, say what it is, who produces it, what it contains, and what it is for, with one instance and without a definition by negation unless the reader would otherwise assume the negated reading. To shorten, cut orientation first, then repetition, process narration, and inventories; keep mechanism, equations, figures, and confirmed examples, and list the categories cut. A later correction narrows an earlier one, and praise for one part approves only that part. Changing a status (to example, candidate, or proposal) adds no criterion, reason, or fact the source lacks; write the status word and stop. Fix the document, never the skill, mid-task.
On an explicit revision or deslop request, name what each suspect sentence does for the reader before editing it; a tell is a functional diagnosis, never an authorship verdict. Keep claim strength, meaningful hedges, and voice, then reread the result for new tells, uniform polish, and drift. A batch revision keeps each author's voice distinct.
Author profile
Read writing profile before drafting or revising anything a colleague will read, and apply it even when no skill was named. A current explicit request or governing template wins over it, and it wins over the defaults here.