nexus

Name: nexus
Availability: InStock
Author: lapagayo

Route canonical Nexus lifecycle commands through a single governed entrypoint.

1|Updated Mar 31, 2026

Search Tags:#routing #cli #orchestration #governance #lifecycle #hosts #nexus

Ready to run

npx skills add https://github.com/LaPaGaYo/nexus --skill nexus-lapagayo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nexus
Source: https://github.com/LaPaGaYo/nexus/tree/main
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill nexus-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Route canonical Nexus lifecycle commands through a single entrypoint to enforce governance and host routing discipline.

Core Features & Use Cases

Route canonical Nexus lifecycle commands through a unified entrypoint to maintain governance guarantees.
Guide session bootstrap by inspecting mounted CCB providers, execution mode, and current session readiness.
Surface runtime state and advisories to downstream skills like design, plan, QA, via manifests and completion advisors.

Quick Start

Initialize a run with /nexus to bootstrap the canonical lifecycle and follow Nexus prompts to select the appropriate execution path.

Frequently Asked Questions about nexus

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

FAQPage Schema

How do I route lifecycle commands through a single entrypoint for multi-host governance?▼

Lifecycle routing through a single entrypoint enforces governance by guiding session bootstrap, inspecting mounted providers, and directing execution paths across Claude, Codex, Gemini, and Factory host surfaces.

What is CLI orchestration for session bootstrap and provider mounting?▼

CLI orchestration for session bootstrap inspects mounted CCB providers, evaluates execution mode, checks session readiness, and selects governed CCB or local provider paths to maintain routing discipline.

How do I initialize a canonical lifecycle run and select an execution path?▼

Initialize a canonical lifecycle run by invoking the entrypoint command to bootstrap the session, then follow the prompts to select the appropriate execution path based on mounted providers and readiness state.

Does lifecycle governance work across different AI host surfaces like Claude and Gemini?▼

Lifecycle governance applies across four host surfaces: Claude, Codex, Gemini, and Factory, enforcing routing discipline and execution-mode selection for each specific platform during session bootstrap.

How does runtime state get exposed to downstream skills like design, plan, and QA?▼

Runtime state exposes execution mode, mounted providers, and session readiness to downstream skills via manifests and completion advisors, ensuring design, plan, and QA skills receive accurate advisories.

When should I choose governed CCB paths over local provider paths?▼

Choose governed CCB paths over local provider paths when session readiness checks and execution-mode selection require strict governance guarantees and routing discipline across the host surfaces.