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/discovery-patterns.md

View on GitHub
# Discovery Patterns

How to detect available MCP tools by capability category during first-run discovery.

## Detection Strategy

List all available MCP tools by checking what's loaded in the current session. MCP tool names follow the pattern `mcp__<server>__<tool>`. Match tool names against these patterns to categorise capabilities.

## Chat Tools

Look for tools that can send and read messages in team channels.

| Pattern | Server | Notes |
|---|---|---|
| `mcp__*google-chat*__chat_messages` | Google Chat | Supports spaces, threads, cards |
| `mcp__*slack*__*message*` | Slack | Channels, threads, blocks |
| `mcp__*discord*__*message*` | Discord | Channels, threads |
| `mcp__*teams*__*message*` | Microsoft Teams | Channels, threads, cards |

**What to capture**: The exact tool name, which server it belongs to, and whether it supports threading.

**Fallback**: If no chat tools are found, the skill outputs formatted text for the user to copy-paste into their preferred channel.

## Git

Not an MCP tool. Detect with:

```bash
git rev-parse --is-inside-work-tree 2>/dev/null
```

If true, git is available. Capture the repo name from the directory or `git remote get-url origin`.

## Issue Trackers

| Pattern | Server | Notes |
|---|---|---|
| `mcp__*github*__github_issues` | GitHub | Issues and PRs, labels |
| `mcp__*linear*__*issue*` | Linear | Issues, projects, labels |
| `mcp__*jira*__*issue*` | Jira | Issues, projects |
| `mcp__*erpnext*__erpnext_issues` | ERPNext | Issues with client scoping |

**What to capture**: Tool name, whether it supports creating issues, available label schemes.

## Task Trackers

| Pattern | Server | Notes |
|---|---|---|
| `mcp__*asana*__*task*` | Asana | Tasks, projects |
| `mcp__*linear*__*issue*` | Linear | Also serves as task tracker |
| `mcp__*todoist*__*task*` | Todoist | Tasks, projects |
| `mcp__*tuesday*__*task*` | Tuesday | Workspaces, boards, items |

## Knowledge

| Source | Location | Notes |
|---|---|---|
| Basalt Cortex | `~/Documents/basalt-cortex/` | Clients, contacts, knowledge — grep to search |

**What to capture**: Whether Basalt Cortex vault exists and has relevant data.

## Discovery Output

After detection, present a summary to the user:

```
## Discovered Capabilities

- Chat: Google Chat (via google-chat-anthro)
- Git: Yes (jezweb/my-project on branch main)
- Issues: GitHub (via github MCP)
- Tasks: Brain (via brain MCP)
- Knowledge: Vault (via vault MCP)

Missing:
- (none — all capabilities available)

Which chat space should I post updates to?
```

If multiple options exist for a category (e.g. two chat servers), ask the user which one to use.

## Re-Discovery

If a tool becomes unavailable after the playbook was saved (MCP server disconnected), the skill should:

1. Note the missing tool in its output
2. Fall back gracefully (skip that data source, or output text instead of posting)
3. Suggest updating the playbook if the change is permanent
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