async-instead

# Async Instead Skill "This meeting could have been an email" is true more often than the email would have worked — because async fails without structure: the doc nobody read, the thread that discussed forever and decided never. A working conversion replaces the meeting's *functions*, not just its slot: information transfer becomes a doc with a read-by date; discussion becomes a bounded comment window; decision becomes an explicit closure step with a named decider and a deadline — the part async most often fumbles and the part this skill enforces. And some things genuinely need rooms; the honest list is part of the design. ## What This Skill Produces - **The conversion design** — the meeting's functions mapped to async mechanisms, with owners and deadlines - **The artifact format** — the update-doc or decision-doc template that carries the load - **The closure protocol** — how the async thread *ends*: the decider, the deadline, the decision recorded - **The still-sync list** — what this meeting does that async can't, and the smaller room that remains ## Required Inputs Ask for these if not provided: - **The meeting being converted** — its functions in honest proportion (how much status vs. discussion vs. decision vs. the social glue) - **The team's async maturity** — do docs get read here? Are comment deadlines respected? Conversion designs differ for teams with and without the muscle (and building the muscle starts smaller) - **The tools** — where docs live, where comme...