guild-hall

Reorganizes a flat directory of reference documents into layered subdirectories that support progressive discovery. Use when a single directory has accumulated enough docs that "all in one place" is hindering navigation rather than helping it, when readers can't tell where to start, or when the user explicitly asks to "stratify", "layer", "rearrange for progressive discovery", or "split this directory into categories". Triggers include phrases like "too many files in one directory", "no clear entry point", "hard to find the why", "where do I start reading".

Consult the guild's craft knowledge compendium for reference material relevant to the current task. Use when starting a code review, writing a spec, writing a plan, making design decisions, conducting research, beginning implementation from a plan, writing a commission prompt, working with TypeScript patterns, generating images, designing visual assets, conducting strategic analysis, setting up a new project's architecture, designing a CSS color system, building with the Claude Agent SDK, or entering any domain the compendium covers. Triggers include "check the compendium", "consult reference", "craft guidance", "reference entries".

Propose a new compendium entry when you notice a knowledge gap during work. Use when the compendium doesn't cover a domain you need, when a topic would benefit from a reference entry, when you encounter a recurring pattern that should be documented, or when no compendium entry exists for a topic you're working in. Triggers include "compendium gap", "propose entry", "needs a reference entry", "compendium doesn't cover this".

Review completed commission artifacts as a batch, extract loose threads into a retro, and delete the commission files. Use after a feature's implement-review-fix cycle completes, before creating a PR, or when .lore/work/commissions/ (or the flat-layout .lore/commissions/) has accumulated files that no longer represent active work. Triggers include "clean up commissions", "commission cleanup", "review commissions", "batch cleanup".

Review completed meeting artifacts as a batch, extract untracked decisions into a retro, update memory, and delete the meeting files. Use when .lore/work/meetings/ (or the flat-layout .lore/meetings/) has accumulated closed meetings, after a feature push with multiple meetings, or periodically to keep the directory current. Triggers include "clean up meetings", "meeting cleanup", "review meetings".