ren-os

Use when the friend wants to back up their wiki to a private remote, or check backup status. Triggers on /ren:backup with optional subcommands (--setup, --tarball, --status). Git push primary, tarball fallback.

Use when the friend wants to start a brand-new project's memory — nothing to scan yet, just a name. Triggers on the /ren:bootstrap-project slash command. Stamps the shared wiki skeleton (additive) and queues an empty L2 pointer-map for the project. For an EXISTING repo with real code/git history, use /ren:ingest-project instead.

Use when the friend wants a structural map of a codebase (call graphs, symbol index, cross-file references) — beyond what wake-up/recall already surface from the wiki. Triggers on /ren:code-map [build|status]. A thin wrapper over Graphify (pinned 0.9.x), never a second hand-rolled engine; gracefully absent if Graphify isn't installed.

Use when the friend wants a framework health check, or after /ren:update to confirm nothing broke. Triggers on /ren:doctor. Runs a battery of small, isolated checks (env, wiki structure, frontmatter, schema versions, budget lint, dangling L2 pointers, graphify status, backup configuration, global-tier drift, harness neutrality) — all warn-not-block.

Use when the friend wants to bring an EXISTING project (real code/git history) into their wiki as an L2 pointer-map. Triggers on the /ren:ingest-project slash command (optional [path]). A read-only scanner mines the repo for facts; the live session drafts compact knowledge + pointers from those facts; this skill assembles and queues the map, then shows the friend the first-session artifact — the visible proof memory was captured (spec §3.8 A-10). For a brand-new project with nothing to scan, use /ren:bootstrap-project instead.

Use for first-time setup of RenOS, or to resume a partial setup. Triggers on the /ren:install slash command. Idempotent guided flow: environment check, wiki bootstrap, optional interview, backup nag, companion offers, first project, then a closing summary of what's now possible. Every stage is skippable except wiki bootstrap; re-running skips whatever's already done.

Use to build or update the friend's identity + working-style profile. Triggers on the /ren:interview slash command, or delegated to from /ren:install's onboarding flow. Asks ONLY from a capped, skippable question list — every question is optional, the whole interview can be skipped, and every unanswered field gets a sane default. No venture/founder questions in this default path.

The §3.5 minimal metric-watch routine. Watches four signals — injection budget growth, memory growth rate, classifier fail-closed events, and backup configuration — and writes findings to the journal for the next wake-up to surface. Triggers on /ren:metric-watch, or (recommended) a weekly scheduled routine.

Use when the friend wants to reactively pin or correct memory mid-session: "remember it like THIS" or "that's wrong, drop it." Triggers on the /ren:pin slash command. The simplest producer in the system — one invocation, one proposal, queued through the single write-queue like every other producer. Not a pipeline.

Use when the friend explicitly wants to look something up in the wiki mid-session, beyond what wake-up already injected. Triggers on the /ren:recall slash command followed by a free-text query. Every fetch this skill performs is logged — that log is the mechanical miss-measurement substrate (spec §3.2), not a surveillance feature.

Use when the friend wants to see what the system remembers about a project (or the wiki overall) — "what do you remember about X", "show me my project memory." Triggers on the /ren:remember [project] slash command. Renders the L2 map in human prose, not a raw markdown dump. The cheapest trust-builder in the scope (spec §3.8 A-10) — read-only, always.

Use when the friend (or a scheduled routine) wants a retrospective pass: mine instrumentation + journal + recent session history for repeated corrections, wrap-gate failures, and repeated task shapes that aren't skills yet — propose each as a queue diff. Triggers on /ren:retrospective [--since <date>]. NOT an eval-scored iteration loop — one deterministic pass, optionally judgment-enriched by the live session before proposing.

Use when the friend wants to declare a pre-declared routine/loop — a scheduled or triggered automation that runs unattended. Documents the v3 routine-spec schema (Task 6.3): every routine must declare its schedule, exit criterion, failure handler, AND a capability/path allowlist bounding WHAT it may touch, not just when it runs. Triggers on the /ren:routine-init slash command.

Use when the friend wants to review pending suggestions: rare, high-stakes items a producer (retrospective, promotion, doctrine, wiki-health) has raised for explicit approve/reject — never auto-applied. Triggers on the /ren:suggestions slash command. The single interactive decide surface over lib.suggestions' durable store (Task 14); this is where an accepted decision actually becomes a write.

Use when the user runs /ren:update to upgrade the framework. Drives the migration state machine — fetches latest version, classifies the bump, snapshots the wiki, runs migrations, verifies via verify.json, shows diffs for approval, applies, and re-verifies. Snapshot/rollback is built in. Never silent on MAJOR bumps.

Use when the friend (or a scheduled routine) wants a coherence check on the wiki: dangling L2 pointers, contradicting pages, duplicate pages, numeric drift between facts, a mass-deletion anomaly scan, and the quarantined/unreviewed-content inventory. Triggers on /ren:wiki-health. This is 0.3's replacement for per-write human approval (v2.2 removed the queue gate on data-plane writes) — the autonomous auditor that runs periodically instead of a human reviewing every diff.

Use when a wiki page's schema_version is behind the registry's current version for its page type. Owns the minimal schema registry (schemas.json) and a thin verify/apply primitive for running one migration directory against one page. Invoked by /ren:update, not directly by the friend.

Use at session end when the friend wants to consolidate what happened. Triggers on the /ren:wrap slash command. Writes an L1 narrative summary (always, auto-quarantined as unreviewed) and gates candidate durable items through a fail-closed classifier, auto-applying them (revertible) unless held for a contradiction or surfaced as a promotion suggestion. Most sessions produce zero durable candidates — the discipline is bias toward NOT durable, per spec §3.1.