skills.rest
Thrimbda
ThrimbdaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

legion-wiki

Consolidate cross-task knowledge into a stable .legion/wiki layer.

13|1|Updated Feb 7, 2026
Search Tags:#decisions#patterns#wiki#knowledge-management#writeback#cross-task#task-summaries
One-click install
npx skills add https://github.com/Thrimbda/legion-mind --skill legion-wiki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legion-wiki
Source: https://github.com/Thrimbda/legion-mind/tree/main/skills/legion-wiki
Command: npx skills add https://github.com/Thrimbda/legion-mind --skill legion-wiki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legion wiki layer centralizes cross-task knowledge from raw task docs into .legion/wiki, providing stable decisions, reusable patterns, and maintenance signals while preserving task-level traces.

Core Features & Use Cases

  • Centralizes cross-task decisions, patterns, and maintenance notes into the wiki at .legion/wiki.
  • Creates task-level summaries under .legion/wiki/tasks to anchor context and enable search.
  • Enforces wiki writeback as a closing step in the Legion workflow to ensure durable knowledge capture.

Quick Start

Update the Legion wiki with a concise task summary and the current cross-task decisions for the most recently completed task.

Frequently Asked Questions about legion-wiki

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

FAQPage Schema
How do I consolidate cross-task decisions and patterns into a centralized knowledge base?▼

Cross-task decisions and patterns are consolidated into a centralized knowledge base by building and updating the .legion/wiki layer, which centralizes raw task docs into stable, reusable references.

What is the best way to maintain a wiki layer for task summaries and maintenance signals?▼

Maintaining a wiki layer for task summaries involves applying a unified wiki lifecycle that enforces mandatory closing writeback, ensuring durable knowledge capture and clear separation from raw task docs.

How does wiki writeback work when closing completed development tasks?▼

Wiki writeback works as a mandatory closing step in the workflow, requiring you to update the .legion/wiki layer with concise task summaries and current cross-task decisions upon task completion.

Do I need to separate raw task documentation from my consolidated wiki content?▼

Separating raw task documentation from consolidated wiki content is required to preserve task-level traces while providing stable decisions, reusable patterns, and maintenance signals in the .legion/wiki layer.

When do I need to query cross-task knowledge for software engineering projects?▼

Querying cross-task knowledge is needed when searching for stable decisions, reusable patterns, or maintenance signals across multiple completed tasks, using the .legion/wiki layer as the central reference.

Can I create task-level summaries to anchor context and enable search across my project?▼

Task-level summaries can be created under .legion/wiki/tasks to anchor context and enable search, applying the wiki lifecycle to centralize cross-task knowledge from raw task docs.

Related Skills

Explore More Software Engineering Skills→
oaustegardoaustegard
137

versioning-skills

Initialize Git repositories and commit changes for skill directories.

Community
Basic
blocknaviblocknavi
1

convex-agents

Build persistent, stateful AI agents with thread management and tool integration in Convex.

Official
Intermediate
Biztactix-RyanBiztactix-Ryan

pm-do

Claim unassigned tasks, retrieve parent story context, and update statuses via ProjectMan's MCP server.

Community
Intermediate
steven508508steven508508
1

byterover

Manage and retrieve AI agent knowledge stored in Markdown files.

Community
Advanced