kriswill

Backport existing plans into the Obsidian daily journal. Use when plans exist in the vault but are missing journal entries.

Estimate the scope and runtime of the frontmatter backfill — hardware specs, vault size, pending upgrades, and a calibrated time estimate. Read-only; nothing is modified.

Upgrade existing vault notes to the current frontmatter standard (type, date, duration_s, normalized model + context_window) so they appear in the managed Obsidian bases. Interruptible and resumable.

Display all configuration options with their effective value and which config layer set them.

Display current session details including ID, duration, turn counts, token usage, and tool stats.

Toggle session document capture on or off. Use /session on, /session off, or /session to toggle.

Rewrite the Obsidian daily journal for a selected day from existing plan/summary notes. Use when journal entries are missing, corrupted, or need regeneration.

Migrate vault date directory layout to match the configured scheme. Use when changing date_scheme in capture-plan.toml and existing vault directories use a different layout.

Maintain the knowledge/ OKF bundle — the repo's authored knowledge layer (patterns, decision records, playbooks, component catalog). Use after adding or changing modules/packages/hosts, when making a non-obvious design decision worth recording, or when asked to "update the knowledge bundle", "add a decision record", "validate the bundle", or "regenerate the knowledge graph".

Extract an in-tree Nix package/derivation into its own flake-parts sub-flake (under flakes/<name>/) that the root flake consumes via a relative-path input — the stepping stone to later splitting it into a separate repo with a one-line URL swap. Use this skill whenever the user wants to modularize or split a Nix flake or reorganize packages: "turn this derivation into its own flake", "extract <pkg> into a sub-flake", "make <pkg> a standalone / in-repo flake", "split pkgs/<x> out", "prep <pkg> to move to its own repo", "modularize the flake", or is moving things from pkgs/ into flakes/. Covers the whole procedure end to end — scaffold, wire the root (relative-path input + follows), test (standalone build + parity + flake check), adversarial quality review, and documentation. Bundled bun/TypeScript scripts (inventory.ts, scaffold.ts, verify.ts) do the rote steps.

Update or fix the ccglass Nix derivation for a new upstream release. Clone the latest upstream tag, scan the source for bun-compile hazards, write/test the fork patch, then build and verify the flake's ccglass package (binary + MCP + dashboard) on aarch64-darwin. Use when bumping ccglass, regenerating its patch, or troubleshooting its build.

Cut a flake-explorer release (patch/minor/major) via the Release workflow — changelog grooming, dispatch, the manual-approval gate, and post-publish verification. Use when the user asks to release, cut/publish a version, or bump the package.