switch-clients

Purpose

Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.

Before investigating or acting:

1. Read the task context contract.
2. Read the method.

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.