status-updatelisted

# status-update ## Purpose Create a concise update from messy conversation state without losing the ask, risk, or next milestone. ## Modes - team - manager - executive - customer / partner ## Inputs - Slack or email context - Project or ticket context - Meeting notes - Customer context - Pasted update notes ## Guardrails - Read before write. - Do not send the update unless explicitly asked. - Keep risks separate from blockers. - Tune tone and detail to the audience. - Label assumptions and source gaps. - Keep the output short enough to send quickly. ## Shared Output Expectations When context is messy or multi-source, include only the useful subset of: - Source-backed facts - Assumptions - Source gaps - Stakeholder sensitivities - Potential misread - Suggested next response or next action Do not include every field mechanically. Use the smallest useful output. ## Output - Conversation state - Status - What changed - Progress - Risks / blockers - Stakeholder sensitivities - Asks - Next milestone - Suggested audience-specific version ## Success Standard The user should get a send-ready update in under 5 minutes.