Plan a vendor transition using documented readiness
Use only information supplied in the conversation and this skill text. Do not browse, call tools, inspect files, execute code, create artifacts, or take external actions. Return the work directly in chat. Attribute material claims to supplied source labels or quotations; a pasted URL is a source label, not evidence that its contents were checked. Distinguish supplied facts, reasonable interpretations, proposals, and unknowns.
Inputs and scope: Use the outgoing and incoming service scope, agreements, desired transition window, customer ownership, supplied access attestations, dependencies, approval evidence, continuity requirements, and fallback arrangements. Do not request credentials. If a decision-changing input is absent, ask the smallest useful question and complete the portions supported by available material. State assumptions explicitly; do not manufacture facts, approvals, dates, or completion evidence.
Method 1. Define what is moving, who owns the service and business outcomes, and what remains with each party. Label components required, optional, out of scope, or unknown using the supplied scope rather than assuming a standard migration package. 2. Map commercial and operational commitments, including notice periods, overlap, termination dependencies, data or service handover, acceptance, and payment timing described in supplied agreements. Flag conflicting commitments without offering legal conclusions. 3. Create an ownership and access-attestation register listing asset or service, customer owner, delegated role, stated status, evidence source, and gap. Documented assertions are not technical verification; exclude passwords and secret-handling workflows. 4. Assess continuity needs and transition dependencies: service availability, records, support coverage, training, integrations described by the user, and fallback capacity. Identify which unresolved item would block the proposed transition decision. 5. Define a readiness review with required evidence, named decision authority if supplied, acceptance criteria, rollback triggers, rollback owner, and monitoring owner. Proposed criteria remain proposals until agreed; document review cannot establish launch approval. 6. Sequence preparation, review, transition-window coordination, and stabilization as a human plan. State what is supported, uncertain, and dependent on external checks; do not inspect accounts, change billing or DNS, deploy, or claim cutover readiness has been technically verified.
Output: Return scope dispositions, commitment and ownership matrix, dependency plan, documentary readiness gaps, proposed decision criteria, rollback and monitoring responsibilities.
Quality checks: Verify required versus optional scope, ownership evidence, approval status, commercial timing, continuity, and fallback responsibilities. Keep an approved plan distinct from successful execution and a supplied attestation distinct from a completed check.
Worked example: A payroll provider transition requires historical records, customer-owned administrator access, and a parallel payroll review. The supplied packet confirms records export but has only an email claiming access, and no parallel-review result. Mark export supported, access attested but unverified, and parallel review missing. Recommend resolving required evidence before the decision; do not certify a safe payroll cutover.