Wiki zone manager for BCOS. Ingests URLs / local docs / inbox captures into docs/_wiki/ as schema-validated pages with banner citations, three structural shapes for source-summary, and two-tier refresh. Schema-driven, CLEAR-governed, derived-artifact. Invoke with /wiki.

Creates implementation plans for ALL work scenarios. MANDATORY entry point for the PLAN phase. 8-step workflow: Intent -> Discovery -> Scenario -> Context -> Template -> Approach -> Session -> Approval 2 scenarios: AGENTING (ecosystem work), DOCUMENTATION (context creation & refinement)

Extracts structured context from conversation exports (Slack, meeting transcripts, chat logs) into _inbox for processing.

Strategic reflection skill. Step back from daily work to think about the bigger picture of your context architecture, identify gaps, and envision improvements.

Validates documentation quality: markdown syntax, cross-references, JSON structure. WHEN TO USE: - Validating markdown files for quality issues - Checking cross-references between documents - Validating JSON structure in ecosystem files - As part of FIXED END validation in any scenario WHEN NOT TO USE: - Content quality auditing (use context-audit for that) - Making content changes (findings guide manual fixes)

Agent ecosystem expert for creating, maintaining, and auditing agents and skills. Prevents ecosystem drift and overlap.

Periodic maintenance of institutional knowledge. Analyzes lessons for staleness, overlaps, and gaps. Keeps lessons.json healthy.

Single-task dispatcher for CLEAR Context OS scheduled maintenance. Runs from the daily scheduled task, reads schedule-config.json, determines which jobs are due today, runs them in sequence, appends to the diary, writes a consolidated morning digest, and surfaces any frequency-tuning suggestions. WHEN TO USE: - Invoked automatically each morning by the `bcos-{PROJECT}` scheduled task - User says "run today's maintenance now" (manual dispatch) - User says "run the [job-name] job" (runs one job on demand, skips others)