skills/hangy-source-grounded-writing/references/operations-writing.md

# Operations Writing Route

## Meeting agendas and proposals

For each agenda item, write:

1. background and why the topic is being raised;
2. the current process or confirmed facts;
3. the problem or risk observed;
4. the proposed process or options;
5. the exact decision the meeting must make;
6. owner, timing, or next action when known.

Separate `confirmed fact`, `current operating plan`, and `new proposal`. Make the distinction visible when readers could confuse them.

## Notices

- Lead with the action recipients must take.
- Include who, what, by when, where, and how.
- Explain only the context needed to secure cooperation.
- Match the user's friendly but concrete tone.
- Make links and attachments easy to identify.

## Feedback-only requests

- Read the full artifact and surrounding context.
- Select the requested number of high-impact points.
- Explain the issue, why it matters, and a concrete revision.
- Do not write into the source document until the user explicitly asks.

## Live document edits

Preserve tables, lists, and page flow. When asked to implement the text, use the installed `hangy-safe-document-edit` skill on the current host when it is available, create a copy, edit the copy only, and render the full result. If that skill or the required file tools are unavailable, provide copy-ready replacement text plus a manual structure-and-render QA checklist, and do not claim that the file was edited or verified.