Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.
Start a fresh conversation. Replace the highlighted placeholders.
Use switch-clients to transition from the current engagement to [target customer and intended workspace], ensuring any unfinished work is left in a recoverable state. Verify the new binding with a fresh sanitized resume packet and return the selected customer, binding evidence, and the next action for the new engagement.
Required inputs
[target customer and intended workspace]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: switch-clientsdescription: Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.
switch-clients
Purpose
A refreshed client binding and cross-client triage.
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
Principles
This task operates on existing engagement records. Use the local CLI and permitted sanitized packets; do not invent a portfolio or initialize records merely to complete the task. Report missing records or access as a limitation.
If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.