skills.rest
LaPaGaYo
LaPaGaYoCOMMUNITY
Explore all skills by this author →
GitHub

plan-ceo-review

Route lifecycle commands through the Nexus alias to the canonical /frame command.

1|Updated Mar 31, 2026
Search Tags:#routing#lifecycle#alias#frame#nexus#command-dispatch#canonical-path
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill plan-ceo-review-lapagayo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-ceo-review
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/aliases/plan-ceo-review
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill plan-ceo-review-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a lightweight transitional alias that routes lifecycle commands to the canonical Nexus /frame path without introducing extra contracts or transition logic.

Core Features & Use Cases

  • Routes lifecycle commands through a stable alias to the canonical frame path.
  • Ideal for projects that want to preserve existing workflows while avoiding duplicate logic or artifacts.
  • Use Case: when you need to reference the canonical lifecycle path via the plan-ceo-review alias without changing internal routing.

Quick Start

Run /frame through the plan-ceo-review alias to initiate the canonical lifecycle.

Frequently Asked Questions about plan-ceo-review

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

FAQPage Schema
How do I route lifecycle commands to a canonical path without adding new contracts?▼

To route lifecycle commands without adding new contracts, apply an alias that delegates to the canonical Nexus /frame path. This transitional alias preserves existing workflows while avoiding duplicate logic or artifacts.

What is a transitional alias for lifecycle command routing?▼

A transitional alias is a lightweight routing path that directs lifecycle commands to the canonical Nexus /frame path. It provides a stable reference without introducing extra transition logic or duplicate artifacts.

How do I initiate the canonical lifecycle through the plan-ceo-review alias?▼

To initiate the canonical lifecycle through the alias, run the /frame command via the plan-ceo-review routing path. This delegates execution to the canonical frame path while inheriting Nexus governance and safety checks.

Does the alias routing inherit Nexus governance and safety checks?▼

Yes, alias routing inherits Nexus governance and safety checks. Because the alias delegates directly to the canonical /frame path, all governance and safety validations applied to the frame path remain active.

When should I use an alias instead of directly modifying internal routing?▼

Use an alias when you need a stable routing path to reference the canonical lifecycle without changing internal routing. It is ideal for projects that want to preserve existing workflows while avoiding duplicate logic.

Are there limitations to using a transitional alias for command dispatch?▼

The transitional alias is limited to routing existing lifecycle commands to the canonical path. It does not introduce new contracts, artifacts, or transition logic, so it cannot handle new routing requirements outside the frame path.

Related Skills

Explore More Software Engineering Skills→
LaPaGaYoLaPaGaYo

plan-eng-review

Route Nexus frame commands through the canonical /frame surface.

Community
Basic
LaPaGaYoLaPaGaYo

frame

Generate framing artifacts defining scope, success criteria, and governance for Nexus initiatives.

Community
Advanced
LaPaGaYoLaPaGaYo

ship

Automate release gating and merge readiness governance in Nexus.

Community
Advanced
drhazemibclcdrhazemibclc

workflows-work

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

Community
Basic