legion-docs

Classify task information into per-task documents and cross-task wiki.

13|1|Updated Feb 7, 2026

Search Tags:#workflow #documentation #handoff #RFC #auditability #task-contracts

Ready to run

npx skills add https://github.com/Thrimbda/legion-mind --skill legion-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legion-docs
Source: https://github.com/Thrimbda/legion-mind/tree/main/skills/legion-docs
Command: npx skills add https://github.com/Thrimbda/legion-mind --skill legion-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

LegionMind's documentation governance helps teams place task information into the correct per-task files (plan.md, log.md, tasks.md, docs/*.md) and centralizes cross-task knowledge in the wiki, ensuring auditability and preventing info drift.

Core Features & Use Cases

Provides explicit guidance on where decisions, progress, and artifacts belong.
Keeps raw task evidence under .legion/tasks/** and cross-task knowledge under .legion/wiki/** for reuse.
Supports RFCs, reviews, and handoffs to enable replay, rollback, and verification.

Quick Start

Create or update the task's plan.md with a clear contract and link design RFCs in the Design Index so future agents can reproduce and audit the task.

Frequently Asked Questions about legion-docs

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

FAQPage Schema

How do I maintain auditable documentation for multi-agent workflows?▼

To maintain auditable documentation for multi-agent workflows, classify task information into specific per-task files like plan.md, log.md, and tasks.md, while centralizing cross-task knowledge in a wiki to prevent info drift and support replay.

What is the best way to structure task handoffs and RFCs for safe delegation?▼

Structuring task handoffs and RFCs for safe delegation requires placing task contracts in plan.md and linking design RFCs in a design index, enforcing document boundaries so future agents can reproduce and verify work safely.

How do I organize per-task documents to prevent information drift?▼

Organize per-task documents to prevent information drift by keeping raw task evidence under .legion/tasks/** and cross-task knowledge under .legion/wiki/**, applying explicit guidance on where decisions, progress, and artifacts belong.

Can I use this approach for tasks without stable contracts?▼

This approach applies to per-task work with stable contracts, RFCs, reviews, and handoffs. Tasks lacking stable contracts may not benefit from the enforced document boundaries and design indexing required for auditability and replay.

Why do I need a design index linking to RFCs in my documentation?▼

A design index linking to RFCs is needed to support auditability and safe delegation, ensuring future agents can reproduce and verify the task by providing a clear, centralized reference for design decisions and archival practices.