More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Team Ownership Transition Review

    1

    Team Ownership Transition Review is a ToolForge Labs workflow for team or role ownership transitions, recurring duties, access, dependencies, escalation, and acceptance evidence.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Team Ownership Transition Review

    Team Ownership Transition Review

    Example session with this skill installed

    An operations lead leaves in two weeks. She owns three vendor renewals, a monthly customer SLA report, the admin account for a shipping portal, and an undocumented Friday reconciliation spreadsheet. Her manager assigned the renewals to Finance but has not assigned the SLA report, portal access, or reconciliation process.

    • Read your context and instructions
    • Compiled the team ownership transition

    TRANSITION NOT READY

    Case analyzed

    An operations lead leaves in two weeks. She owns three vendor renewals, a monthly customer SLA report, the admin account for a shipping portal, and an undocumented Friday reconciliation spreadsheet. Her manager assigned the renewals to Finance but has not assigned the SLA report, portal access, or reconciliation process.

    This review uses only the supplied facts. It does not assume access to production systems, private records, vendor portals, or approvals that were not provided.

    Verified evidence

    • VERIFIED: The operations lead leaves in two weeks.
    • VERIFIED: Vendor renewals were assigned to Finance.
    • VERIFIED: The SLA report has no successor.
    • VERIFIED: Shipping portal admin access has no successor.
    • VERIFIED: The Friday reconciliation is undocumented and unassigned.

    Concrete findings

    1. Only the visible renewal work has a successor; three operational obligations remain orphaned.
    2. The portal account is both an access risk and a continuity risk, while the reconciliation process is hidden knowledge that may fail after departure.
    3. The current record is not safe to close merely because work has started or a status label says complete; closure must follow the evidence and acceptance condition for this exact case.
    4. The next action should repair the missing decision/evidence boundary without rewriting history or inventing facts that were not available at the time.

    The controlling rule for this case is

    An ownership transition is complete only when responsibilities, recurring obligations, access, dependencies, escalation paths, and evidence of acceptance move to named owners without leaving hidden work attached to the departing team or person.

    The supplied facts are sufficient for a concrete case verdict, but not for claiming approvals, delivery, acceptance, or test results that were not supplied.

    Required actions

    1. Inventory renewals, SLA reporting, portal administration, and reconciliation together.
    2. Assign primary and backup owners for the SLA report with cadence and evidence.
    3. Transfer portal administration using approved identities rather than shared credentials.
    4. Document reconciliation inputs, steps, outputs, and exceptions, then have the successor perform one observed run.
    5. Record escalation contacts for each recurring obligation.

    Deterministic validation

    • Every recurring duty has a primary owner and cadence.
    • The successor uses their own approved portal identity.
    • A successor produces one SLA report and one reconciliation result.
    • Managers verify ownership rather than relying on verbal handoff.

    Validation must use this exact scenario, not a generic substitute. Preserve the dates, owners, amounts, systems, dependencies, customer promises, or source records that make the case materially different.

    Evidence boundaries

    • UNKNOWN: Whether the portal supports multiple admins.
    • UNKNOWN: The exact SLA deadline and recipient.
    • UNKNOWN: Whether the spreadsheet contains macros or credentials.
    • UNKNOWN: Who reviews reconciliation exceptions.

    These unknowns do not erase the conclusion. They define the exact evidence needed before closure without guessing.

    Decision and handoff

    Keep the case open until the stated acceptance condition is evidenced, the responsible owner is identifiable, and any remaining exception is explicit. Record the outcome beside the original evidence so a later reviewer can see what changed, who approved it, and which condition was actually satisfied.

    If the decision changes later, preserve the superseded reasoning rather than silently overwriting it. A later reviewer should be able to reconstruct the chain from original request to evidence, decision, action, and verification.

    Closure rule

    Close only when the requested result is supported by evidence. No completed action, customer acceptance, approval, production verification, or passing test is claimed unless it was actually supplied in this case.

    Additional acceptance detail 1

    Because this case establishes that the operations lead leaves in two weeks., the closure record should also show that the related action was completed in a traceable way: Inventory renewals, SLA reporting, portal administration, and reconciliation together. The evidence should be attached to the same case or linked with a stable identifier, not left only in chat, memory, or an unreferenced status field.

    Additional acceptance detail 2

    Because this case establishes that vendor renewals were assigned to Finance., the closure record should also show that the related action was completed in a traceable way: Assign primary and backup owners for the SLA report with cadence and evidence. The evidence should be attached to the same case or linked with a stable identifier, not left only in chat, memory, or an unreferenced status field.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Team Ownership Transition Review is a ToolForge Labs workflow for team or role ownership transitions, recurring duties, access, dependencies, escalation, and acceptance evidence. Produces a concrete case verdict, verified evidence, missing gates, corrective actions, deterministic validation, and a defensible closure rule without inventing approvals, external access, execution, or outcomes. It performs the supplied case directly, separates verified evidence from unknowns, produces bounded actions, and keeps validation tied to the exact scenario instead of returning an empty template.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    Cannot verify external shipping status or bank transfers without provided evidence logs. Limited to analyzing the specific commitment text provided.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files

    Use a controlled review workspace or supplied evidence. Review owner decisions and any proposed changes before operational action.

    Listed1 month ago
    Updated14 days ago

    What's inside

    Frequently Asked Questions

    This skill audits team and role handovers to ensure no recurring duties or dependencies are missed, providing a deterministic verdict on whether a transition is complete and defensible.

    The skill returns a comprehensive case verdict, a list of verified evidence versus missing gates, specific corrective actions, and a defensible closure rule based on the provided scenario.

    This skill is designed as a standalone logic workflow compatible with major LLMs and AI agents that support structured text analysis and ToolForge Labs standard formatting.

    No, this is a diagnostic and validation tool; it reviews and verifies provided evidence but does not perform actual system access, external execution, or grant official approvals.

    Your purchase includes the core transition review workflow, the deterministic validation logic, and documentation for integrating the skill into your operations or supply chain pipelines.

    Unlike generic templates, this skill performs direct validation of your specific data, separating verified facts from unknowns to ensure the transition is grounded in reality.

    New in Business & Operations