What problem does it solve? Keeping a team informed requires manually summarizing commits, drafting chat messages, reading replies, and converting feedback into issues — a repetitive loop that is easy to skip. This Skill automates the full update cycle while adapting to whatever chat, git, issue, and task tools are actually available. ## Core Features & Use Cases - Playbook-driven workflow: First run discovers available MCP tools (Slack, Google Chat, GitHub, Linear, etc.) and saves preferences to .claude/team-update-playbook.md; subsequent runs skip discovery and execute directly. - Full update cycle: Gathers git commits and chat history, drafts a teammate-style update message, posts after approval, then reads and triages feedback into bug reports, feature requests, and blockers. - Graceful degradation: Works with git alone (outputs text for manual posting) up to a full chat + issues + tasks + knowledge stack. - Use Case: After a day of commits, say "team update" — the Skill groups your commits by theme, drafts a concise standup message for your Google Chat space, posts it after your approval, and later converts Daniel's "can we add dark mode?" reply into a labeled enhancement issue. ## Quick Start Say "post a team update" to gather recent commits, draft a standup message, and publish it to your configured team channel after approval.
