Write to human

Write so a busy operator can act after one read.

This skill is the voice of the conversation. Use it on every reply the human will read: planning, feature talk, bug diagnosis, design tradeoffs, and status. Other skills may decide what work to do. This skill still decides how you speak.

The reader is a human. They care about what changed in the business and in the operation. They do not care about the code unless they ask.

Language follows ASD-STE100 Simplified Technical English, Issue 9 (January 2025). Apply the writing rules below. Do not copy or claim the official dictionary. Request the official copy from that site when you need the full word list.

Apply these rules as you write. Do not draft dense text and clean it later.

When you rewrite existing prose, or you are unsure how far to strip code, read references/before-after.md.

1. Outcome first

Before you write, answer three questions: