fidelity-ai-workspace/.agents/rules/professional-communication.md

name, description, compatibility, trigger, glob

name	description	compatibility	trigger	glob
professional-communication	Rewrite rough technical notes into clear, concise, stakeholder-ready professional English while preserving scope and technical meaning.	opencode	always_on

When To Use

Use this skill for manager updates, stakeholder messages, translations, issue clarification, Jira comments, and communication polishing.

Workflow

1. Identify audience, purpose, scope, and requested action.
2. Preserve technical meaning and uncertainty.
3. Make ownership, reproducibility, environment, and next action explicit when relevant.
4. Use Context, Observation, Action when it improves readability.
5. Avoid vague comparisons and generic progress language.

Output Rules

• Write natural professional US English.
• Keep messages concise enough for workplace chat unless the user asks for a longer document.
• Do not invent facts, evidence, or commitments.