sync-call-state

name	sync-call-state
description	Record the outcome of a reviewed post-call document in the client's local state, from one confirmation and a visible diff. Computes one new entry for clients/NAME/state.md and, when the call carried a stage signal, a change to the single stage line in profile.md; shows both as a diff, asks Apply / Edit / Cancel, and writes only on Apply. Use after you reviewed the post-call doc and want the client's log and stage to say what was agreed. NOT for drafting the recap or the scope (post-call), for a status board (client-context), or for preparing the next call (prep-call). Model-invocable, so fire it yourself when the goal matches; state what you are about to do and get the operator's confirmation before the mutating step; never fire it as a background checkpoint.
tags	["client","state","stage","post-call","confirm-gated"]
version	1.2.1
author	yonyon-ai
user-invocable	true
complexity	medium
argument-hint	<client-name> [--doc <path>] [--date YYYY-MM-DD]
disable-model-invocation	false
allowed-tools	Read, Edit, Write, Glob, Grep, AskUserQuestion
license	MIT
compatibility	Full file workflow on coding agents with a working directory: Claude Code (verified), Cursor, GitHub Copilot, Windsurf, OpenCode, Codex, Gemini CLI, Antigravity, OpenClaw, Grok Build. Chat mode (Step 0) on hosts without file access: Claude.ai, Claude Desktop, ChatGPT, Grok, Manus, Gemini Spark; paste the inputs, read the outputs, save them yourself, nothing is written. Wispr Flow MCP optional.
supported_agents	["claude-code","cursor","github-copilot","windsurf","opencode","codex","gemini-cli","antigravity","openclaw","grok-build","claude-desktop","claude-ai","chatgpt","manus","gemini-spark","grok"]
metadata	{"display_name":{"he":"עדכון מצב אחרי ביקורת","en":"Confirm-gated state sync"},"display_description":{"he":"אחרי ביקורת של מסמך post-call: diff אחד ליומן המצב ולשורת השלב של הלקוח, נכתב רק אחרי אישור מפורש. שום מערכת חיצונית לא נוגעים בה.","en":"After you review a post-call doc: one diff for the client's state log and stage line, written only after an explicit yes. No external system is touched."},"tags":{"he":["לקוחות","יומן מצב","שלב לקוח","אישור","עברית"],"en":["clients","state-sync","stage","confirm-gated","hebrew"]},"supported_agents":["claude-code","cursor","github-copilot","windsurf","opencode","codex","gemini-cli","antigravity","openclaw","grok-build","claude-desktop","claude-ai","chatgpt","manus","gemini-spark","grok"]}

sync-call-state

A reviewed post-call document in, one confirmed state update out. The skill reads the CallFacts block that post-call wrote, computes one new entry for clients/<client-name>/state.md and, when the call carried a stage signal, a change to the single stage: line in profile.md. It shows both as a diff and writes only after you say Apply. No external system is touched.

Sibling split: post-call drafts the document this skill consumes, client-context reads the state this skill writes, prep-call reads it before the next call. This skill never reads a transcript and writes nothing but the two files above.

When to use

• You reviewed clients/<client-name>/post-call-<date>.md and want the client's log and stage to say what was agreed.
• A call moved the client (first call done, scope proposed, work started, paused, closed) and profile.md still shows the old stage.
• The call changed nothing about the stage but you want the outcome on record.

When NOT to use

• To draft the recap or the scope: post-call.
• To see where a client stands: client-context.
• To prepare the next call: prep-call.
• Before you reviewed the document. The doc is the source of truth here; an unreviewed doc produces an unreviewed state.
• On a transcript, a chat export or your own notes. Only a post-call doc is accepted.

Workflow

Step 0: chat mode (hosts without file access)

On a host that cannot read or write files (Claude.ai, ChatGPT, Grok, Manus, Gemini Spark, or Claude Desktop without a filesystem MCP), run in chat mode: ask the user to paste the reviewed post-call doc (it must carry DRAFTS ONLY and the CallFacts block), the current stage: line and the last state.md entry. Run Step 2, then print the proposal as two paste-ready blocks (the new state.md entry and the new stage: line). Steps 3 and 4 do not run: the user applies the change by hand. No external system is touched in either mode.

Step 1: load the reviewed doc and the client files

Resolve the client folder; a missing clients/<client-name>/ is an error: print cp -r fixtures/clients/_template clients/<client-name> and stop. The doc is , else with from , else today. Refuse the doc when its first line lacks the words DRAFTS ONLY (it was not written by , or was edited past recognition) or when has no fenced JSON block. Read (its line is required) and ; a missing one is an error with the same copy hint. Output: doc path, , current stage, the existing entries of .