Share Internal Doc

Prepare the requested document for its colleagues and verify the usable shared copy. technical-report-writing owns content selection, structure, headings, tables, figures, explanation, and production. This skill adds the recipient and delivery requirements; it does not create a second editorial workflow.

Infer the reader, intended use, existing material, medium, language, and distribution from the request. Reuse context already established by another skill. Review requests return findings; writing and revision requests include the artifact. Ask only for consequential missing user choices.

Document preparation

For writing, substantive revision, or editorial review, read and apply the available technical-report-writing skill, including its normal-path editorial defaults. Pass the established audience, document purpose, sources, medium, and explicit preferences once. A user naming only this skill still receives the complete document or requested review. Do not restart intake or require the user to orchestrate the skills.

If the writer is unavailable, use the established user preferences and reader brief to complete the authorized task with available tools. Report the missing capability only if it materially limits the result; do not silently install a package. For delivery of an already finished document, inspect its recipient suitability and the actual copy without initiating an unrelated rewrite.

Use insight-dashboard for data views whose comparisons and commentary must remain consistent with selections. Use the appropriate document or figure tool for the requested medium. Do not copy their methods into this package or run an automatic second editorial pass. Explicit AI-slop revision and Korean meaning repair live in technical-report-writing (references/authoring-and-revision.md and references/korean-writing.md), and the author's standing preferences in its references/writing-profile.md; apply them through that skill, once.

A colleague must be able to follow the document's actual explanation: identify the subject, connect the example to the finding, understand the condition that changes its meaning, and use the result for the intended task. Read a representative passage from that colleague's position. Supply missing subject context where it is needed; an author introduction or reading tour does not supply that context. Links support verification and further detail. Carry the document's purpose into production: a factual incident record and a technology explanation need different depths. Preserve required records in their owning location.

Apply the project's terminology and presentation choices. When no theme is specified and screen styling is controlled, retain the pack's dark default for the page and figures; requested light, print, and destination-controlled themes take precedence. Pass the actual preference to the production tool.

When colleagues or the user have edited the shared copy, retrieve that version before revision or republication and pass it to the writer as the current baseline. Reconcile differences with a local source before rebuilding; preserve intentional deletions and intervening edits. Familiarity with the original draft is not evidence that the shared copy is unchanged.