legion:workflow-common

Load core workflow logic before optional extensions across Legion commands and adapters.

72|8|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/9thLevelSoftware/legion --skill legion-workflow-common
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legion:workflow-common
Source: https://github.com/9thLevelSoftware/legion/tree/main/skills/workflow-common
Command: npx skills add https://github.com/9thLevelSoftware/legion --skill legion-workflow-common

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compatibility shim to ensure new commands load the core workflow logic before optional workflow-common extensions, enabling stable startup and predictable behavior across runtimes.

Core Features & Use Cases

  • Centralized bootstrapping: load workflow-common-core first and defer optional extensions until needed.
  • Adapter-agnostic orchestration: works with all Legion adapters by enforcing a safe extension loading protocol.
  • Safer integrations: reduces risk of conflicts when adding new commands or extensions.

Quick Start

Load the core workflow first, then optionally load extensions as needed when adding a new command.

Frequently Asked Questions about legion:workflow-common

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

FAQPage Schema
How do I fix workflow extension loading conflicts during CLI startup?

Workflow extension loading conflicts during CLI startup are fixed by enforcing a centralized bootstrapping protocol that loads core workflow logic before any optional extensions, guaranteeing predictable behavior and reducing integration risk.

What is the correct load order for workflow core logic and extensions?

The correct load order requires loading workflow-common-core first, then deferring optional extensions until needed. This strict loading protocol ensures safe extension loading and stable startup across all Legion adapters.

Why does my workflow command fail when extensions load before the core logic?

Workflow commands fail when extensions load before core logic because the bootstrapping problem disrupts the expected runtime environment. Loading core workflow logic first enforces a safe extension protocol and prevents misconfiguration.

Does the workflow bootstrapping protocol work with all Legion adapters?

The workflow bootstrapping protocol works with all Legion adapters by applying adapter-agnostic orchestration. It ensures predictable startup and safe extension loading across diverse runtimes without adapter-specific dependencies.

How do I safely add new commands to an existing workflow without breaking startup?

Safely add new commands by loading the core workflow logic first, then optionally loading extensions as needed. This centralized bootstrapping approach reduces the risk of conflicts and ensures stable startup.