Skip to content

borghei/Claude-Skills / project-management/team-communications

team-communications

Verified

Design a delivery team's communication system — channel routing, meeting-load reduction, status structure, escalation SLAs, timezone norms. Use when the calendar is full, updates go unread, or blockers surface late.

assets/status_update_template.md

View on GitHub
# <Team / Project> — week of <DD Month>

**<GREEN | YELLOW | RED>** — <one clause saying why, with a number in it.>

> The verdict goes in the first sentence. A reader who stops here should still
> know whether to worry. Target: under 400 words total, longest paragraph
> under 80 words, at least three quantified claims.

## Progress

- <What shipped or moved — with a number.> (<metric before → after>)
- <Second item, with a number.>
- <Third item, with a number.>

## Risks

Two only. A list of seven risks tells the reader you have not prioritised.

| Risk | Impact if it lands | Owner | Mitigation by |
|------|--------------------|-------|---------------|
| <risk> | <schedule / scope / cost impact, quantified> | <name> | <date> |
| <risk> | <quantified impact> | <name> | <date> |

## Decision needed

<The choice, in one sentence.>

- **Option A:** <option> — <main cost>
- **Option B:** <option> — <main cost>
- **Recommendation:** <A or B>, because <reason>.
- **Needed by:** <date>. If no decision by then, <what happens by default>.

> If there is genuinely no decision this period, write **"No decisions needed this week."**
> The reader cannot tell the difference between absence and omission.

## Asks

- <Named person>: <specific thing you need> by <date>.
- <Named person>: <specific thing you need> by <date>.

## Next

- <What the team does next period.>
- <Second item.>

---

**Delete before sending:** hedges ("somewhat", "mostly", "should be fine",
"hopefully", "we think"), jargon ("leverage", "synergy", "circle back",
"bandwidth"), and any green status you could not defend in a room.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall