workflows-work

Redirect deprecated /workflows:work alias to /ce:work command.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/drhazemibclc/plate --skill workflows-work-drhazemibclc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflows-work
Source: https://github.com/drhazemibclc/plate/tree/main/.codex/skills/workflows-work
Command: npx skills add https://github.com/drhazemibclc/plate --skill workflows-work-drhazemibclc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The legacy /workflows:work alias creates confusion by pointing to an outdated workflow path; this Skill redirects users to the supported /ce:work command to maintain consistency.

Core Features & Use Cases

  • Redirects the deprecated alias to the new /ce:work command to ensure seamless operation.
  • Provides deprecation guidance and transition tips for existing prompts and integrations.

Quick Start

Invoke the deprecated /workflows:work alias to trigger a redirect to /ce:work.

Frequently Asked Questions about workflows-work

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

FAQPage Schema
How do I redirect a deprecated workflow alias to a new command?

To redirect a deprecated workflow alias, this Skill intercepts prompts using the legacy /workflows:work path and automatically routes them to the supported /ce:work command, ensuring seamless operation.

Why does my legacy /workflows:work alias no longer execute workflow tasks directly?

The legacy /workflows:work alias no longer executes directly because it is deprecated. The Skill disables direct model invocation for the legacy command and provides deprecation guidance to transition your prompts.

What happens when I invoke an outdated workflow alias path?

When you invoke an outdated workflow alias path, the Skill triggers an automatic redirect to the supported /ce:work command, providing transition tips and maintaining workflow consistency for existing integrations.

Can I still use my existing prompts that reference the /workflows:work path?

Yes, existing prompts referencing the /workflows:work path still function. The Skill intercepts these prompts, applies alias redirection, and seamlessly transitions the workflow task to the supported /ce:work command.

What is the best way to transition integrations from a deprecated alias?

The best way to transition integrations from a deprecated alias is to let the Skill automatically redirect calls from /workflows:work to /ce:work, providing deprecation guidance while ensuring a smooth transition without breaking existing prompts.

Are there limitations when using alias redirection for deprecated workflow commands?

A limitation of alias redirection is that direct model invocation for the legacy /workflows:work command is explicitly disabled, meaning the deprecated path cannot execute tasks independently without routing to /ce:work.