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

workflows-plan

Redirect legacy workflows-plan requests to the /ce-plan planner.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Redirects legacy workflow planning requests that relied on the deprecated workflows-plan alias to the modern /ce-plan planner, preserving backward compatibility.

Core Features & Use Cases

  • Backward compatibility: Ensures existing workflows invoking workflows-plan continue to work by routing them to /ce-plan.
  • transitional guidance: Helps teams transition to the recommended /ce-plan alias with minimal disruption.
  • Use Case: A developer has a saved integration that calls workflows-plan; the system will generate an actionable plan via ce-plan.

Quick Start

Invoke /ce-plan with your ARGUMENTS to generate a structured workflow plan.

Frequently Asked Questions about workflows-plan

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

FAQPage Schema
How do I migrate deprecated workflow planning requests to the new planner?▼

Migrate deprecated workflow planning requests by routing them to the ce-plan planner, which preserves backward compatibility while redirecting legacy workflow-plan alias invocations to generate structured planning steps.

Can I still use the legacy workflows-plan alias to generate feature plans?▼

Yes, the legacy workflows-plan alias remains functional for generating feature, bug fix, or improvement plans by automatically mapping ARGUMENTS input to the ce-plan planner without disrupting existing integrations.

What is backward compatibility support for legacy workflow planning transitions?▼

Backward compatibility for legacy workflow planning transitions ensures existing saved integrations calling the deprecated alias continue working by routing requests to the ce-plan planner with minimal disruption.

How do I transition my team's workflow planning to ce-plan?▼

Transition workflow planning to ce-plan by invoking the planner directly with ARGUMENTS, generating structured workflow plans while the system maintains transitional guidance for legacy alias users.

Does ce-plan support arguments from deprecated workflow planning integrations?▼

ce-plan supports arguments from deprecated workflow planning integrations by mapping the ARGUMENTS input directly, allowing existing projects and teams to generate actionable plans seamlessly.

Why does my legacy workflows-plan alias redirect to a new planner?▼

The legacy workflows-plan alias redirects to ce-plan because the old alias is deprecated, requiring transition to the modern planner while preserving backward compatibility for existing workflow planning requests.

Related Skills

Explore More Software Engineering Skills→
0xDarkMatter0xDarkMatter
29

project-planner

Detect stale project plans and suggest /plan commands from git activity.

Community
Basic
hydrosolutionshydrosolutions
1

issue-planning

Create local draft issue files with acceptance criteria and implementation steps.

Official
Intermediate
thisisryanswiftthisisryanswift
2

lfg

Coordinate autonomous software feature planning, implementation, review, and integration.

Community
Advanced
kubiyabotkubiyabot
16

test-skill

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

Official
Basic