team-update

# Team Update Post project updates to team chat, read and triage feedback, and plan next steps. Adapts to whatever communication and project tools are available. ## The Playbook Pattern This skill uses a **playbook** file at `.claude/team-update-playbook.md` in the project root. - **First run**: Discover available tools, ask the user for preferences, execute, save a playbook - **Subsequent runs**: Read the playbook, skip discovery, execute directly - **User edits playbook**: Changes take effect immediately (channel, style, triage rules) The playbook is plain markdown the user can edit. It captures tool configuration, channel preferences, message style, triage rules, and last-run metadata. --- ## Phase 0: Playbook Check Check if `.claude/team-update-playbook.md` exists in the project root. **If it exists**: Read it. All tool configuration, channel info, message style, and triage rules are in there. Jump to Phase 1 with known config. **If it does not exist**: Run Phase 0b (Discovery) first. --- ## Phase 0b: Discovery (First Run Only) Detect available capabilities by checking what MCP tools are connected and what local tools exist. Read [references/discovery-patterns.md](references/discovery-patterns.md) for detection patterns. ### Capability Detection Check for each capability category: | Capability | How to detect | Fallback if missing | |---|---|---| | **Chat** | MCP tools matching `chat`, `slack`, `discord`, `teams` | Output formatted text for manual posting...