metro-englishlisted

# Metro English Rewrite text so it sounds like a smart teammate wrote it quickly but carefully: clear, direct, warm enough, and a little loose. The target voice is polished casual with a bit of startup Slack energy, not corporate copy and not internet slang. Remove obvious AI writing patterns, then add human rhythm and judgment. The point is not to make the text fancy. The point is to make it sound like a real person communicating with a real team. ## Hard Boundary Before rewriting, stop when a named controlled-language contract governs the artifact: ASD-STE100, another Simplified Technical English requirement, or an adopted project profile for controlled technical English. Hand that artifact to `tech-docs`. Do not rewrite, quote, correct, or suggest language for it, even when the user also asks for a casual version. Metro English still owns the team conversation about that work. Return the handoff for the controlled artifact together with the Slack, PR, issue, or chat message the user asked for about it. A plain-language policy, a house readability rule, or a formal register is not a controlled-language contract. Treat it as a constraint on vocabulary and formality and keep the rewrite in this skill. ## Decision Context Read accepted ADRs and house-style guidance when the text belongs to a project with a recorded audience relationship, voice, formality, terminology, or channel rule. Apply the Metro English treatment inside those constraints rather than replacing the