Skip to content

jezweb/claude-skills / plugins/dev-tools/skills/team-update

team-update

Verified

Post project updates to team chat, gather feedback, triage responses, and plan next steps. Adapts to available tools (chat, git, issues, tasks). First run discovers tools and saves a playbook; subsequent runs execute from the playbook. Trigger with 'team update', 'post update', 'sync with team', 'standup', 'check team chat', 'feedback loop', 'project update', 'what did the team say'.

references/playbook-format.md

View on GitHub
# Playbook Format

Save this file at `.claude/team-update-playbook.md` in the project root. Fill in all sections based on discovery results and user preferences. Mark unavailable capabilities as "Not available".

## Template

```markdown
# Team Update Playbook

Generated by the team-update skill. Edit this file to change behaviour.

## Channel

- **Type**: [Google Chat | Slack | Discord | Teams | Manual (no chat tool)]
- **MCP tool**: [tool name, e.g. mcp__google-chat-jez__chat_messages | "none"]
- **Space/Channel**: [name] (ID: [space/channel ID])
- **Thread strategy**: [new-message | continue-thread | thread-per-day]
- **Identity**: [Post as self | Post as Anthro Morphic | other]

## Data Sources

### Git
- **Repo**: [repo path or "current directory"]
- **Branch filter**: [all | main only | specific branches]

### Chat (Read)
- **MCP tool**: [tool name for reading messages | "same as Channel"]
- **Read scope**: [same channel as posting | additional channels]

### Issues
- **Type**: [GitHub | Linear | Jira | Brain | none]
- **MCP tool**: [tool name | "none"]
- **Repo/Project**: [owner/repo or project name]
- **Create labels**: [bug, enhancement | custom labels]

### Tasks
- **Type**: [Brain | Asana | Linear | none]
- **MCP tool**: [tool name | "none"]
- **Project filter**: [project name | "all"]

### Knowledge Store
- **Type**: [Vault | Brain | none]
- **MCP tool**: [tool name | "none"]
- **Tags**: [tags for storing/retrieving update history]

## Message Style

- [Lead with what shipped, not process]
- [Group commits by theme, not individual hashes]
- [Keep under N lines for chat, use card format for bigger updates]
- [Address team members by first name]
- [Sign-off: none for chat, name for email]
- [Tone: conversational | formal | brief]

## Triage Rules

| Feedback type | Action | Tool |
|---|---|---|
| Bug report | Create issue (label: bug) | [issue tool] |
| Feature request | Create issue (label: enhancement) | [issue tool] |
| Question | Draft reply for approval | [chat tool] |
| Blocker | Flag immediately | Present to user |
| Acknowledgement | Note, no action | - |
| Off-topic | Ignore | - |

## Team Context

- [Name]: [Role/area — helps with triage and @mentions]
- [Name]: [Role/area]

## Last Run

- **Date**: [ISO 8601 timestamp with timezone]
- **Thread key**: [thread ID or key if applicable]
- **Summary**: [1-2 line summary of what was posted]
- **Feedback processed**: [yes/no, count of items triaged]
```

## Section Notes

### Channel
- **Thread strategy**: `new-message` posts a fresh top-level message each time. `continue-thread` replies to the same thread. `thread-per-day` creates one thread per day.
- **Identity**: If using a bot identity (like Anthro), include any sign-off or persona rules.

### Data Sources
- Mark any unavailable source as `"none"` so the skill skips it cleanly.
- For Git, `all` branches is usually correct for dev updates; `main only` for production-focused updates.

### Message Style
- These are freeform guidelines the user can edit. The skill reads them as instructions.
- Common additions: "Include PR links", "Mention blockers first", "Use emoji for status".

### Triage Rules
- The table maps feedback types to actions. Users can add custom rows.
- The "Tool" column tells the skill which MCP tool to use for that action.

### Last Run
- Updated automatically after each successful post.
- The skill uses the date to determine the time window for gathering context.
- If this section is missing or empty, the skill asks the user how far back to look.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall