sandsower

Use when the user asks to babysit a PR, run /babysit, keep a PR green, monitor review/CI until ready, or optionally close out a PR through configured merge/capture/retro automation. Can run directly; host goal/persistence support is optional.

Audit Beislið workflow config and probe each capability. Use when the user says "doctor", "/doctor", "audit my config", "check my workflow", "probe everything", "what's set up", or after editing workflow.md. Reports gaps in conversational prose; does not modify config or skills. Pass `--refresh` to force re-probing even if the cache is fresh.

Author, approve, and export execution envelopes for AFK slices in a standalone strong-model session. Use only when the user explicitly invokes /envelope with a ticket id, approved Work Contract/spec file, or batch. Other skills may recommend it but must never auto-route into it. Ends with an approved, validated, repo-committed bundle under .beislid/exports/ that an external runner executes later.

Use when you have an approved design or requirements for a multi-step task, before writing code. Creates a file-level implementation plan with TDD as the default rhythm, host-agent task tracking, and parallel task batching.

Use when starting work on a ticket after checking out the feature branch. Fetches the ticket, explores the codebase, routes vague tickets through spec, routes large work through break-spec, then hands implementation-ready work to blueprint and implement. Adapts to whatever ticket tracker and domain tooling the environment provides — driven by `<repo>/.beislid/workflow.md`.

Use when the user says "ready-for-review", "ready for review", "prepare for review", or "finalize for review", or when work is ready for PR review handoff. Bookend to kickoff: gates, review, final check, and PR handoff. Do NOT use for mid-implementation commits or unfinished work. Reads workflow.md and probes capabilities lazily.

Use when the user says "retro", "/retro", "retrospect", "post-run retro", "tune workflow", "refine gates", "improve workflow.md", or asks what should change after a run. Reviews available run/session evidence and the whole `.beislid/workflow.md`, then recommends workflow improvements. Does not edit config; route accepted changes through `setup`.

Use when the user says "review-response", "respond to review", "review comments are back", or "QA sent feedback", or when existing PR review comments or QA feedback need a response. This is the post-review response skill. Do NOT use when the user wants to write reviews, start new work (use kickoff), or create a PR (use ready-for-review). Reads `<repo>/.beislid/workflow.md` and probes lazily. Supports prompt profiles for agent-ready review comments.

Search Memento Vault for day-to-day recall, past decisions, discoveries, implementation history, and prior session context. Use when the user asks "do you remember", "have we seen", "what did we decide", "what did we learn", "where was this implemented", "find prior context", "check memory", "search the vault", or any question that depends on prior work rather than current files alone.

Archive artifact bundles in Memento Vault. Use when the user says preserve, archive, or save generated artifacts, or wants evidence bundles kept intact instead of turned into atomic notes.

Initialize orra in the current repo. Runs orra_setup, installs all stock directives, and adds vault-bridge when memento-vault is available. Use when Vic says "init orra", "orra setup", "set up orra here", or invokes /orra-init.

Recover recent working context from local state and Memento Vault. Use when the user asks to continue, resume, pick up where they left off, or find prior work.

Run or preview Memento Vault consolidation. Use when the user asks to consolidate, find patterns, run inception, preview clusters, or synthesize cross-session themes.

Review Memento Vault for stale low-value notes and archive confirmed candidates. Use for periodic vault maintenance.

Capture durable knowledge from the current work session into Memento Vault. Use when the user asks to remember, save, capture, or record decisions, discoveries, bug fixes, or reusable patterns.

Checkpoint useful session knowledge and pending work before starting a fresh context. Use when the user asks to start fresh, checkpoint, save and reset, or clear context.