walm00

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)

Manage the BCOS self-learning ladder: list learned rules, forget a rule, regenerate learned-rules.json from resolutions.jsonl. Mechanical-only — reads/writes derived artifacts; the actual learning happens via record_resolution.py at click time. Invoke with /learning.

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

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

Cross-zone retrieval and task-driven bundle resolution for BCOS. /context search ranks docs across every zone in one shared schema; /context bundle (P5) returns a curated, freshness-flagged, source-of-truth-aware context bundle for a declared task. Mechanical-first; LLM is opt-in via --semantic / --resolve-conflicts / --verify-coverage flags only. Invoke with /context.

The single entry point for getting anything new into your context architecture. Takes any input (documents, URLs, YouTube, meeting notes, pasted content) and triages it: dump to _inbox, park in _planned, or integrate into active docs. WHEN TO USE: - "Here's a document — integrate it into my context" - "Save this for later" / "Dump these meeting notes" - "I have an idea — park it somewhere" - "Read

First-run onboarding skill. Gets a new user from zero to a working context system. Claude asks one direct question upfront to pick the right scaffolding, then works from what the user shares — no long assessment ceremony beyond that. Creates a checklist that tracks setup progress across sessions and self-removes when done. WHEN TO USE: - "I want to set up my business context" - "Here's my website

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

Bootstrap skill - enforces proactive skill discovery and invocation. Automatically check for applicable skills before any action. Always active.

Wiki zone manager for BCOS — the universal long-form and cross-cutting content destination per plugin-storage-contract.md Rule 2. Stores runbooks, SOPs, decision logs, how-tos, glossaries, post-mortems, FAQs, meeting notes, and plugin cross-cutting context (charters, transcripts, research, customer-call notes). Two ingest paths: Path B (local files, pasted text, inbox promotion — runbooks/scripts/

Shared TodoWrite patterns for consistent progress tracking across all BCOS skills. This is a PATTERN LIBRARY, not an invocable skill. Skills copy these patterns inline. WHY INLINE, NOT INVOKED: If todo-utilities were invoked as a Task(), its TodoWrite calls would execute in an isolated context — invisible to the user. Patterns must run IN the parent skill's main context where TodoWrite is visible.