cadence-syncopate

Redirect legacy emergency session exit commands to /cadence double-time.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/prompted365/context-grapple-gun --skill cadence-syncopate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cadence-syncopate
Source: https://github.com/prompted365/context-grapple-gun/tree/main/cgg-runtime/skills/cadence-syncopate
Command: npx skills add https://github.com/prompted365/context-grapple-gun --skill cadence-syncopate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a legacy entrypoint for an emergency session exit flow, redirecting users to a more current command.

Core Features & Use Cases

  • Legacy Alias: Supports older workflows by mapping to /cadence double-time.
  • User Notification: Informs the user that they are using a legacy command and recommends the preferred alternative.
  • Use Case: A user accustomed to an older command structure invokes /cadence-syncopate during a critical moment, and the system gracefully handles the transition to the current emergency exit procedure.

Quick Start

Run /cadence-syncopate to initiate an emergency session turnaround.

Frequently Asked Questions about cadence-syncopate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a legacy emergency session exit command used for?

A legacy emergency session exit command provides backward compatibility by redirecting older workflow triggers to a current emergency termination procedure. It ensures older command structures gracefully transition to the active session exit flow.

How do I execute an emergency session turnaround using a legacy alias?

To execute an emergency session turnaround using a legacy alias, invoke the legacy command to trigger the redirect. The system notifies you of the legacy status and maps the request to the current emergency exit sequence.

Does the legacy emergency session exit command notify users about deprecated status?

Yes, the legacy emergency session exit command notifies users about its deprecated status upon invocation. It explicitly informs the user they are using a legacy command and recommends the preferred alternative.

When do I need to maintain backward compatibility for session termination workflows?

You need to maintain backward compatibility for session termination workflows when users are accustomed to older command structures during critical moments. This ensures uninterrupted emergency exit procedures without breaking existing automation.

Can I use the legacy syncopate command instead of the current emergency exit procedure?

Yes, you can use the legacy syncopate command instead of the current procedure. It functions as a direct alias, redirecting your request to the active emergency exit command while maintaining full session termination functionality.

Why does the legacy session exit redirect to a new command instead of executing directly?

The legacy session exit redirects to a new command to maintain backward compatibility while consolidating the emergency exit logic. This approach preserves older workflows without duplicating the active termination sequence implementation.