rail-kit

Render a fixed status board for one client from the files in clients/NAME/ (profile, state log, post-call docs, cheatsheets, outreach, notes), the client's row in an optional CRM export, and Wispr Flow meeting titles when that MCP server is connected. The board shows stage, last contact with staleness, direction agreed, open threads, next steps and the sources consulted. Use as the opening read before touching a known client, or to answer where you stand with them. A disagreement between sources is flagged with both values, never resolved. NOT for a pre-call cheatsheet (prep-call), for drafting a recap and scope after a call (post-call), or for changing the stage or the state log (sync-call-state). Read-only, nothing is written. Model-invocable, so fire it yourself when the goal matches; do not fire it speculatively or as a checkpoint.

Turn one client call into a reviewed document with the call facts, a short recap message and a one-page scope, drafted in the client's language (Hebrew by default). Use right after a call when a text transcript exists (a file, or a Wispr Flow meeting through its MCP) and you want the follow-up written before you forget it. NOT for preparing a call (prep-call), for a status board (client-context), or for recording the outcome in the client's state log (sync-call-state). Model-invocable, so fire it yourself when the goal matches; drafts only, nothing is sent; state what you are about to do and get the operator's confirmation before the mutating step; never fire it as a background checkpoint.

Build a one-page cheatsheet for the next call with a client from what the client folder already holds. Who they are, where things stand, the open threads, two to four goals for the call, the questions to ask, what to say when they push on price, timing or scope, and the one next step to propose, in the client's language and register (Hebrew by default). Use right before a scheduled call, once clients/NAME/ exists, whether it is the first call or the fifth. NOT for drafting the recap and scope after a call (post-call), for a status board when no call is ahead (client-context), or for writing an outcome into the state log (sync-call-state). Reads local files, an optional CRM export and Wispr Flow meeting titles; writes one new file and never overwrites. Model-invocable, so fire it yourself when the goal matches; do not fire it speculatively or as a checkpoint.

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.