legion:workflow-common-core

Resolve execution context for /legion: commands including adapter detection and state paths.

72|8|Updated Mar 1, 2026

Search Tags:#workflow #core #command-mapping #legion #adapter-detection #state-paths #settings-resolution

Ready to run

npx skills add https://github.com/9thLevelSoftware/legion --skill legion-workflow-common-core

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legion:workflow-common-core
Source: https://github.com/9thLevelSoftware/legion/tree/main/skills/workflow-common-core
Command: npx skills add https://github.com/9thLevelSoftware/legion --skill legion-workflow-common-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a lean, always-loaded foundation that centralizes adapter detection, state path resolution, settings defaults, and agent loading for all /legion: commands. This core ensures a consistent execution context across command activations, reducing duplication and errors in higher-level workflows.

Core Features & Use Cases

Always-load core conventions for every /legion: command, including adapter detection, state path canonicalization, and baseline mappings.
Resolve canonical state file paths under .planning/ and resolve settings.json defaults safely when missing or invalid.
Resolve AGENTS_DIR once per invocation and load personality files to seed agent behavior.
Provide a stable command-to-skill mapping and context budget ceilings to coordinate multi-step workflows.

Quick Start

Load this core before invoking any /legion: command to ensure adapters, paths, and mappings are resolved.

Frequently Asked Questions about legion:workflow-common-core

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

FAQPage Schema

How do I resolve canonical state paths and settings for automated workflow commands?▼

Canonical state paths and settings defaults are resolved by loading a core execution context that safely handles missing or invalid settings.json and canonicalizes paths under .planning/ for reliable command activation.

What is adapter detection and how does it work during command activation?▼

Adapter detection works by resolving the core execution context once per invocation, identifying the correct environment adapters to ensure consistent state path resolution and baseline command-to-skill mapping across command activations.

How do I load agent personality files and resolve AGENTS_DIR for my workflow?▼

Agent personality files are loaded and AGENTS_DIR is resolved once per invocation by a core execution context that seeds agent behavior, ensuring stable multi-step workflow coordination and reliable operation.

Do I need to load a core module before invoking higher-level workflow commands?▼

Yes, you need to load a lean, always-loaded core before invoking higher-level commands to ensure adapters, state paths, settings defaults, and baseline mappings are resolved for a consistent execution context.

Why does my command-to-skill mapping fail during multi-step workflow coordination?▼

Command-to-skill mapping fails without a stable core execution context that provides baseline mappings and context budget ceilings, which are required to coordinate multi-step workflows and reduce execution errors.

What is the best way to centralize settings defaults and state path resolution?▼

The best way to centralize settings defaults and state path resolution is using an always-loaded core that applies canonical state paths and safe settings.json defaults across all command activations to reduce duplication.