Lw Orchestrator

LLM Wiki Orchestrator

Use this as the top-level coordinator skill when an agent is asked to build, maintain, or answer from a wiki for an arbitrary project or code repository.

Purpose

This skill does not replace the individual skills. It tells the agent which specialized skill to use and in what order.

Canonical workspace contract

Every wiki workspace should use:

• raw/
• wiki/
• .llm-wiki/

Optional:

• outputs/ for non-canonical artifacts when the workspace needs exports, reports, slides, charts, or automation logs

Every wiki workspace should also define:

• .llm-wiki/profile.json
• an active project profile markdown file
• workspace instructions such as AGENTS.md and optionally CLAUDE.md, SOUL.md, or IDENTITY.md

Which skill to use

Initialize a new wiki workspace

Use:

1. lw-init
2. choose or create a project profile
3. add workspace instructions from the templates

Ingest new source material

Use:

1. lw-ingest
2. lw-compile
3. lw-lint
4. lw-reflect when the change is broad or synthesis-worthy

Sync from a repo

Use:

1. lw-sync-repo
2. lw-compile
3. lw-lint
4. lw-reflect when needed

Build or refresh from a Git URL (no existing local checkout)

Use when the user supplies only a remote URL (or the workspace mirror is missing).

1. lw-init if the workspace layout does not exist yet
2. lw-clone-repo — clone into raw/upstream, bind repo_sync in the profile and manifest
3. lw-sync-repo
4. lw-compile
5. lw-lint
6. lw-reflect when needed

Answer questions from the wiki

Use:

1. lw-ask
2. lw-output only when the user wants a non-canonical artifact/export rather than a canonical wiki page

Produce durable outputs

Use:

1. lw-ask if discovery is needed first
2. lw-output

Repair or audit the wiki

Use:

1. lw-lint
2. lw-reflect
3. lw-merge when duplicates or overlap should be consolidated

Agent rules

• Read wiki/SCHEMA.md, wiki/index.md, and recent wiki/log.md before major work.
• Use the active profile to decide authority ranking, taxonomy, watched paths, and drift rules.
• Do not write compiled knowledge outside wiki/.
• Do not bypass raw/ and manifest state for new source ingestion.
• Keep contradiction handling explicit.
• For repo-backed wikis, do not mutate the source repo unless the user explicitly asks.
• Treat outputs/ as non-canonical; promote durable knowledge from outputs into wiki/ during maintenance when needed.