9thlevelsoftware/legion/workflow-common
- community
Checking that the SKILL.md file is still in the repository.
DEPRECATED compatibility shim; workflow-common-core is canonical for all conventions referenced here
Install
npx vskill@latest install 9thlevelsoftware/legion/workflow-commonSKILL.md
Legion Workflow Common (DEPRECATED)
DEPRECATED — DO NOT USE FOR NEW COMMANDS.Canonical source:skills/workflow-common-core/SKILL.mdfor CLI detection, adapter reference, user interaction, settings resolution, agent path resolution, and state file locations.Migration path: Legacy references toworkflow-common.mdin commands, skills, or agent files MUST be updated to point atworkflow-common-core/SKILL.md(always-load) plus the specificworkflow-common-{domain}extension (github, memory, domains) needed. When every reference has migrated, this file SHOULD be deleted.Precedence rule: Any content in this file that diverges fromworkflow-common-core/SKILL.md(agent counts, division lists, settings keys, protocol steps) is STALE. Trustworkflow-common-core/SKILL.md— not this file.The sections below are retained verbatim for legacy pointer compatibility only. They are NOT the source of truth.
CLI Detection and Adapter Loading
Legion supports multiple AI CLIs through an adapter layer. Before any command executes, the active CLI must be detected and its adapter loaded.
Detection Protocol
Adapter Reference Convention
Throughout skills and commands, adapter fields are referenced with dot notation:
adapter.spawn_agent_personality— how to spawn an agent with personalityadapter.model_execution— which model to use for executionadapter.global_config_dir— where global config lives (e.g.,~/.claude/legion/)adapter.commit_signature— Co-Authored-By line for commitsadapter.ask_user— how to present choices to the user
These resolve to the active adapter's Tool Mappings table at runtime.
User Interaction Convention
All commands use adapter.ask_user for user prompts. This maps to:
- Claude Code:
AskUserQuestiontool (structured questions with labeled options) - Codex CLI / Gemini CLI / Cursor / Windsurf / Aider / Kiro / OpenCode / Copilot CLI: plain numbered lists printed to stdout when the runtime does not offer a better structured question surface
- Other CLIs: per adapter's Interaction Protocol section
Commands reference adapter.ask_user in their process body. The allowed-tools frontmatter retains the Claude Code tool name (AskUserQuestion) for backward compatibility.
State File Locations
| File | Path | Purpose | |
|---|---|---|---|
| PROJECT.md | .planning/PROJECT.md | Project vision, requirements, constraints, decisions | |
| ROADMAP.md | .planning/ROADMAP.md | Phase breakdown with agent assignments and progress | |
| STATE.md | .planning/STATE.md | Current position, recent activity, next action | |
| Templates | skills/questioning-flow/templates/ | Schema files for generating PROJECT/ROADMAP/STATE | |
| Phase Plans | .planning/phases/{NN-name}/ | Plan and summary files per phase | |
| Compacted Summaries | .planning/phases/{NN-name}/{NN}-COMPACTED.md | AI-compacted phase summaries preserving decisions and outcomes while trimming verbose details (via memory-manager skill) | |
| PORTFOLIO.md | {adapter.global_config_dir}/portfolio.md | Global portfolio registry — all Legion projects | |
| Milestone Summaries | .planning/milestones/MILESTONE-{N}.md | Completion summaries with metrics per milestone | |
| Milestone Archive | .planning/archive/milestone-{N}/ | Archived phase directories from completed milestones | |
| Memory Outcomes | .planning/memory/OUTCOMES.md | Agent performance and task outcome records for cross-session learning | |
| Memory Patterns | .planning/memory/PATTERNS.md | Successful patterns with reuse criteria — distilled from agent outcomes (via memory-manager skill) | |
| Memory Errors | .planning/memory/ERRORS.md | Error signatures mapped to known fixes — troubleshooting reference for agents (via memory-manager skill) | |
| Memory Preferences | .planning/memory/PREFERENCES.md | User decision signals (accepted/rejected/modified proposals) for preference-informed agent routing (via memory-manager skill) | |
| Custom Agents | agents/{agent-id}.md | User-created agent personality files (via /legion:agent) | |
| Codebase Map | .planning/CODEBASE.md + .planning/codebase/ | Structured architecture doc plus retrieval index generated by /legion:map | |
| Campaign Documents | .planning/campaigns/{campaign-slug}.md | Structured campaign plans with objectives, messaging, audience, channels, calendar, and agent assignments (via marketing-workflows skill) | |
| Design Documents | .planning/designs/{project-slug}-system.md | Structured design system specifications with tokens, components, accessibility, and agent assignments (via design-workflows skill) | |
| Exploration Documents | .planning/explorations/YYYY-MM-DD-{slug}-design.md | Design discovery outputs from /legion:explore sessions (via polymath-engine skill) | |
| Spec Documents | .planning/specs/{NN}-{phase-slug}-spec.md | Structured specification documents produced by spec-pipeline skill before coding phases |
Settings Resolution Protocol
Legion commands MAY be configured via settings.json in the repository root. This file is optional.
When settings are present, command skills must honor them instead of hardcoded values.
Agent Personality Paths
All 52 built-in agent personalities live under agents/ in the plugin root (not necessarily the user's CWD). The path must be resolved before use:
Agent IDs include their division as a prefix (e.g., engineering-senior-developer, testing-qa-verification-specialist). Exceptions: Spatial Computing agents use descriptive prefixes (xr-, visionos-, macos-, terminal-) and Specialized agents use domain prefixes (agents-, data-, lsp-) for shorter, more readable filenames.
Divisions: Engineering, Design, Marketing, Product, Project Management, Testing, Support, Spatial Computing, Specialized, Custom
Custom agents created via /legion:agent follow the same path pattern.
To load an agent personality: Read {AGENTS_DIR}/{agent-id}.md
Pre-Flight Alignment Agent
Polymath (agents/polymath.md)
- Role: Pre-flight alignment specialist
- Invoked by:
/legion:explorecommand - Purpose: Turn raw ideas into a saved design document before optional formal planning
- Key behaviors: Context inspection, research-first workflow, focused structured choices, approach comparison, design-doc output
- Division: Specialized
- Task types: exploration, clarification, research-first, structured-questions, gap-detection
Agent Path Resolution Protocol
Before loading ANY agent personality file, resolve AGENTS_DIR once per command invocation.
Legion agents are installed via the npm installer (npx @9thlevelsoftware/legion). Resolution checks these locations in order:
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 93 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/workflow-common/SKILL.md
Popularity
- Repository stars
- 62
- Repository forks
- 7
- 7-day trend score
- 21
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/9thlevelsoftware/legion/workflow-common)