Communication Style
Make technical communication easy to act on. Preserve evidence, caveats, and required governance fields; remove only material that does not change the reader's decision or next action.
Workflow
- Open with the answer, decision, or observed result. Include the central caveat immediately when it changes the call.
- Choose structure from the content: prose for causality, numbered steps for a sequence, bullets for parallel facts, and headings for genuinely distinct sections.
- Keep connected reasoning together. If statements depend on “because,” “but,” or “so,” express that relationship instead of splitting it into fragments.
- Put evidence next to the claim it supports. Distinguish observations, interpretations, and recommendations.
- Cut repeated summaries, generic preambles, hype, theatrical labels, and advice the reader already supplied.
- End when the request is answered. Add a final recommendation only when the response weighs a real decision.
Boundaries
- Concision never overrides required security findings, uncertainty, approval conditions, commands, test evidence, or rollback instructions.
- Do not manufacture confidence or remove qualifications to make prose sound decisive.
- Do not force every response into headings or bullets.
- Do not copy an external style guide verbatim; apply these repository-owned principles to the current audience and task.
Output check
Before sending, verify that the first two sentences contain the result, every section changes understanding or action, and no conclusion is repeated in a second format.
1---2name: communication-style3description: Write concise, calm technical responses whose structure matches the decision, evidence, or sequence being communicated. Use when drafting substantial plans, reviews, findings, documentation, or completion summaries.4license: Apache-2.05---67# Communication Style89Make technical communication easy to act on. Preserve evidence, caveats, and required governance fields; remove only material that does not change the reader's decision or next action.1011## Workflow12131. Open with the answer, decision, or observed result. Include the central caveat immediately when it changes the call.142. Choose structure from the content: prose for causality, numbered steps for a sequence, bullets for parallel facts, and headings for genuinely distinct sections.153. Keep connected reasoning together. If statements depend on “because,” “but,” or “so,” express that relationship instead of splitting it into fragments.164. Put evidence next to the claim it supports. Distinguish observations, interpretations, and recommendations.175. Cut repeated summaries, generic preambles, hype, theatrical labels, and advice the reader already supplied.186. End when the request is answered. Add a final recommendation only when the response weighs a real decision.1920## Boundaries2122- Concision never overrides required security findings, uncertainty, approval conditions, commands, test evidence, or rollback instructions.23- Do not manufacture confidence or remove qualifications to make prose sound decisive.24- Do not force every response into headings or bullets.25- Do not copy an external style guide verbatim; apply these repository-owned principles to the current audience and task.2627## Output check2829Before sending, verify that the first two sentences contain the result, every section changes understanding or action, and no conclusion is repeated in a second format.
aryaminus