skills.rest
All-The-Vibes
All-The-VibesOFFICIAL
Explore all skills by this author →
GitHub

workflows-work

Migrate workflow invocations from the deprecated /workflows-work alias to /ce-work.

50|14|Updated Mar 11, 2026
Search Tags:#automation#workflow#compatibility#cli#migration#deprecation#alias-mapping
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill workflows-work-all-the-vibes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflows-work
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/workflows-work
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill workflows-work-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The deprecation of the /workflows-work alias creates confusion and potential breakages when teams upgrade; this skill provides a clear migration path to the /ce-work alias to maintain workflow invocation consistency.

Core Features & Use Cases

  • Provides a migration path from deprecated /workflows-work alias to the supported /ce-work, preserving argument compatibility and reducing upgrade friction.
  • Clarifies deprecation and guides teams through the transition, minimizing disruption to automated CI/CD and local tooling.
  • Supports continued operation by mapping existing plans and tasks to the new alias with no changes to user intent.

Quick Start

Run existing workflows using the new alias: /ce-work <ARGUMENTS>

Frequently Asked Questions about workflows-work

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

FAQPage Schema
How do I migrate workflows from a deprecated CLI alias to a new one?▼

Migrating workflows from a deprecated CLI alias to a new one requires redirecting usage to the supported /ce-work alias. This skill maps existing plans and arguments to /ce-work, ensuring future compatibility while preserving input intent during upgrades.

Why does my workflow invocation break after upgrading the CLI tool?▼

Workflow invocation breaks after upgrading the CLI tool because the /workflows-work alias is deprecated. You must transition to the /ce-work alias to maintain consistency and prevent failures in automated CI/CD pipelines and local tooling.

Can I pass the same plan file and specification arguments to the new alias?▼

Yes, you can pass the same plan file, specification, or todo file path arguments to the new alias. The migration ensures input arguments are correctly passed to /ce-work without altering user intent or requiring changes to existing tasks.

What is the best way to handle deprecation mapping for automated workflow plans?▼

Handling deprecation mapping for automated workflow plans is done by redirecting invocation to the /ce-work alias. This provides a clear migration path, reducing upgrade friction by mapping existing plans to the new alias with built-in compatibility notes.

When do I need to update my workflow aliases for future compatibility?▼

You need to update workflow aliases for future compatibility during upgrade or migration tasks. If your teams rely on the /workflows-work alias to invoke plans, aligning with /ce-work ensures continued operation and prevents disruptions.

Related Skills

Explore More Software Engineering Skills→
WaterplanAIWaterplanAI
31

dr

Forward all arguments from /dr to /dry-run for command validation.

Official
Basic
kubiyabotkubiyabot
16

test-skill

Validate tool invocations and command workflows in a minimal testing environment.

Official
Basic
drhazemibclcdrhazemibclc

workflows-work

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

Community
Basic
All-The-VibesAll-The-Vibes
50

workflows-review

Redirect the deprecated workflows-review alias to the /ce-review route.

Official
Basic