jira-comment-writerlisted

# Jira Comment Writer > "The ability to simplify means to eliminate the unnecessary so that the necessary may speak." > -- Hans Hofmann > "If you can't explain it simply, you don't understand it well enough." > -- Attributed to Albert Einstein ## Core Philosophy A comment on a Jira issue is not a status log for engineers — it is a signal to a project manager or client that something happened, what it means, and what comes next. The people reading these comments care about outcomes, timelines, and decisions. They do not need to know which function was refactored or which library was upgraded. They need to know: **Is this moving? Are we on track? Do I need to do anything?** This skill bridges the gap between technical work and stakeholder communication. You describe what you did in whatever terms come naturally — technical is fine. The skill turns that into a comment your PM or client can read, understand, and act on in thirty seconds. **Voice and tone target (Google Developer Style Guide):** Write like a knowledgeable colleague writing to another professional — conversational, friendly, and respectful, without being stiff or overly casual. Avoid jargon, hedging language ("it would appear", "hopefully", "at this point in time"), and culturally specific idioms ("home stretch", "ball in your court", "move the needle"). Simple, consistent writing also makes comments more accessible to readers with varying levels of English proficiency. **Three things every stakeholder comme