Skill

client-update

Draft a client update message. Clear, professional, honest — covers status, next steps, and any blockers that need client action.

From brand-bond-os

Install

Run in your terminal

npx claudepluginhub brandbondco/brand-bond-os --plugin brand-bond-os

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 25, 2026

Actions

View Source View Plugin View on GitHub View README

Type

When to use

Progress update

Regular check-in, milestone reached

Blocker

Waiting on client input, project can't proceed

Feedback request

Work is ready, need a decision

Scope clarification

New request received, needs to be addressed

Delay notice

Timeline needs to shift, proactive communication

Output format

Every update includes:

STATUS — Where the project is right now (one sentence) DONE — What was completed since last update NEXT — What's happening next and when NEEDS — What we need from the client (if anything)

Short. No corporate filler. No apologies unless genuinely warranted.

/client-update

Drafts a status update message for the client. No fluff, no vague reassurance — what's done, what's next, what we need from them.

What this does

Activates bb-client-comms + bb-studio-ops to produce a client-ready message. Adapts tone to the client's language (Turkish or English) and the situation (routine update, delay, feedback request, milestone reached).

Usage

/client-update [situation summary]

Examples:

/client-update Wonn, brand brief approved, moving to concept phase
/client-update project delayed, waiting on client assets since last week
/client-update concept presentation ready, need to schedule review
/client-update (starts a context intake)

Message types

Type	When to use
Progress update	Regular check-in, milestone reached
Blocker	Waiting on client input, project can't proceed
Feedback request	Work is ready, need a decision
Scope clarification	New request received, needs to be addressed
Delay notice	Timeline needs to shift, proactive communication

Output format

Every update includes:

STATUS     — Where the project is right now (one sentence)
DONE       — What was completed since last update
NEXT       — What's happening next and when
NEEDS      — What we need from the client (if anything)

Short. No corporate filler. No apologies unless genuinely warranted.

Tone rules

Match the client's language
Direct but professional
Never vague ("we're making progress") — always specific ("identity concepts ready by Friday")
If there's a problem, name it clearly and provide a solution in the same message

Connects to

bb-client-comms · bb-studio-ops · bb-ops-slack