---
title: "Client room"
description: "Four skills that keep a client engagement legible: call-to-scope, weekly updates, decision logs and handoff packs."
canonical: "https://www.diginomads.win/skills/client-room"
source: "content/pages/skills/client-room.md"
updatedAt: "2026-11-10"
---

**Level:** Starter

## Skills

| Skill | Trigger | Output | Guardrail |
|---|---|---|---|
| call-to-scope | After a discovery call, before a proposal or quote | Outcome, deliverables, exclusions, assumptions, acceptance checks and open questions | No price or timeline is produced unless the user supplied one. |
| weekly-update | When the weekly client update is due | Status, outcomes shipped, next commitments with dates, blockers and decisions needed | A scope change is labelled before it is absorbed into the plan. |
| decision-log | When a client makes, changes or reverses a decision | A dated entry with the decision, the owner, the options considered and what it changes | The log records what was decided, not what the agent thinks should have been decided. |
| handoff-pack | At the end of a phase, or when someone else takes over | Current state, open work, access, risks, decisions and the first three things to read | Secrets and credentials are referenced by owner, never copied into the pack. |

## Install

1. Create `skills/call-to-scope/`, `weekly-update/`, `decision-log/` and `handoff-pack/` in the client project.
2. Give each skill its own `SKILL.md` with a description written as the moment it should fire: 'after a discovery call', 'when the weekly update is due'.
3. Keep the client's scope, milestone list and decision log in `references/`, not inside the instructions.
4. Run the tests below with a real (redacted) call note. If the scope has no exclusions, the skill is not doing its job.

## Tests

- **Prompt:** Turn these discovery notes into a scope I can send before quoting.
  **Pass:** The output has an out-of-scope section, at least three assumptions and open questions above the deliverables.
- **Prompt:** Write this week's update. The client asked for one extra report on Tuesday.
  **Pass:** The extra report appears in the scope watch as 'change' or 'unknown', not silently in the plan.
- **Prompt:** The client changed the launch date. Log it and tell me what moves.
  **Pass:** A dated decision entry is created, with the affected milestones and the owner of the change.

## Sources

- [Agent Skills specification](https://agentskills.io/specification)
- [Anthropic public skills repository](https://github.com/anthropics/skills)

## Why this pack

Client work fails at the seams: a request that was never scoped, a decision that was never written down, a handoff that lives in someone's head. The work itself is usually fine. The record is not.

This pack makes the record a byproduct of the work. The scope skill runs after the call; the update skill runs weekly; the decision log runs when something changes; the handoff pack runs at the boundary. None of them needs a new tool.

## The rule behind the pack

If it changes the plan, it goes in writing before it changes the plan. That is the whole discipline. A scope that absorbs a new request silently is not a scope; it is a hope.

## Adapting it

- For retainers, add a capacity table to the weekly update: units used, units left, what triggers a new scope.
- For agencies, keep an internal version of the update with the risk line you do not send.
- For fixed-price work, make the change label mandatory in every update, even when the answer is “no change”.

## Failure modes

- **The update becomes a diary.** Cut activity that did not change an outcome.
- **The decision log becomes a blame log.** Record the decision and its owner, not the argument.
- **The handoff pack contains credentials.** Reference the owner and the vault entry; never paste the secret.

## Related

- [Scope a client project from a messy call](/prompts/scope-a-project-from-a-call)
- [Write a weekly update that prevents scope creep](/prompts/weekly-client-update)
- [Turn receipts into a bookkeeping-ready log](/prompts/receipt-log)

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "WebPage",
  "name": "Client room",
  "url": "https://www.diginomads.win/skills/client-room",
  "description": "Four skills that keep a client engagement legible: call-to-scope, weekly updates, decision logs and handoff packs.",
  "isPartOf": {
    "@type": "WebSite",
    "name": "DigiNomads",
    "url": "https://www.diginomads.win/"
  }
}
```