legion-workflow

Gate multi-step work in Legion-managed repositories with design and verification stages.

13|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Thrimbda/legion-mind --skill legion-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: legion-workflow
Source: https://github.com/Thrimbda/legion-mind/tree/main/skills/legion-workflow
Command: npx skills add https://github.com/Thrimbda/legion-mind --skill legion-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Legion-workflow provides a mandatory gate for any non-trivial multi-step work within Legion-managed repositories. It ensures takeover decisions, task restoration, mode sequencing, and disciplined wiki writebacks before exploration or coding begins.

Core Features & Use Cases

  • Gatekeeper and entry-point for Legion-managed repos, asserting Legion control and stabilizing task contracts before work starts.
  • Mode-driven execution: default implementation, approved-design continuation, and heavy design-only paths, with RFCs and reviews governing design and risk.
  • Git-worktree-pr envelope integration: coordinates PR lifecycles, code delivery, and mandatory writebacks to wiki and task docs, ensuring auditability.

Quick Start

Start by invoking the legion-workflow entry to determine takeover eligibility, restore any existing task contract, and then follow the gating sequence to execute RFCs, implement, verify, and write back to the wiki.

Frequently Asked Questions about legion-workflow

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

FAQPage Schema
How do I gate multi-step task execution inside git-worktree pull requests?

Task gating inside git-worktree pull requests requires enforcing design reviews, verification, and wiki writebacks before exploration or coding begins. Legion-workflow applies mandatory design gates and task recovery to stabilize contracts and ensure auditable delivery within the PR envelope.

What is task orchestration for design and implementation phases in Legion-managed repositories?

Task orchestration for design and implementation phases coordinates mode-driven execution, RFCs, and staged gating to vet risk before coding. Legion-workflow acts as the entry-point gatekeeper, asserting control and sequencing default implementation, approved-design continuation, or heavy design-only paths.

Can I restore an existing task contract before starting new work in a Legion-managed repository?

Restoring an existing task contract before starting work is supported by invoking the legion-workflow entry to determine takeover eligibility. It stabilizes prior task states and validates design gates, ensuring proper vetting and recovery before exploration or coding resumes.

How do I enforce RFC reviews and wiki writebacks for staged code delivery?

Enforcing RFC reviews and wiki writebacks for staged code delivery is handled through the git-worktree-pr envelope integration. Legion-workflow coordinates PR lifecycles and mandates documentation writebacks to task docs and wikis, ensuring every design and implementation phase remains auditable.

Does legion-workflow support heavy design-only paths without immediate implementation?

Heavy design-only paths without immediate implementation are supported through mode-driven execution. Legion-workflow routes high-risk or complex requests into RFCs and reviews, governing design phases to ensure proper vetting before any exploration or coding begins.

What are the limitations of relying on ad-hoc task recovery in multi-step repository work?

Ad-hoc task recovery lacks enforced design gates and auditable writebacks, risking unvetted exploration and untracked contract states. Legion-workflow addresses this by mandating takeover eligibility checks, mode sequencing, and wiki documentation within the git-worktree-pr envelope.