communication

Topics in the source

• Concision
• Voice
• Rollout announcements
• AI-authorship marker

Use Mnemopi recall for relevant agent-learned context. For authoritative collected facts, citations, or source verification, use OMP’s vault:// interface; never substitute memory, CQ, or direct backing-file access for the vault. For external communications—including initial issue/proposal bodies and replies—lead with the main point and keep the default short. For longer messages, use Minto Pyramid framing: conclusion first, grouped reasons next, supporting evidence last. For complex proposals, use an issue tree to group non-overlapping concerns, cover necessary scope, and prioritize high-impact branches; omit speculative branches and low-value detail. Keep the problem, recommendation, essential tradeoffs/evidence, and decision needed; cut repetition and tangents. Expand only for accuracy or when requested. Sound like a direct, relaxed colleague, not a formal announcement template. Prefer plain language, contractions, and short paragraphs; use warmth sparingly and naturally. Lead with the outcome or the specific question. Keep Slack updates especially brief; include only the context needed to understand the change or respond. Make status, uncertainty, risk, and the requested next st

This is an excerpt. Refer to the complete source and its current requirements.