cwensel

Shared reference for landing a built RDR implementation: ship branch, update RDR docs, close tracking kata, and run follow-up flight. Not invoked directly; read when RDR landing skills cite it.

Use to land a built but unmerged RDR implementation branch: rebase, fast-forward merge, update RDR status/indexes, close tracker(s), and optionally flight follow-up katas. Trigger for land RDR implementation.

Use to run unattended RDR Stage 8 implementation for one or more coupled RDRs plus roborev triage in one worktree session. Optional flags also ship, close the RDR tracker(s), and flight follow-up katas. Trigger for implement RDR with triage.

Use after an RDR implementation launch leaves open roborev findings. Single-pass unattended triage routes findings to drop, fix-now, kata-bug, or rdr-seed, grounded against one or more coupled RDRs. Trigger for roborev triage after launch.

Use to verify a Kata Flight setup. Read-only health check for the .kata-flight seam, marker vars, engine layout, context root, optional RDR binding, and skill links. Trigger for diagnose Kata Flight, check Kata Flight setup, $kata-flight-doctor, or /kata-flight-doctor.

Use to triage kind:rdr-seed kata backlog before running rdr-seed. Classifies seeds as one-RDR, split, collapse, demote, out-of-scope, or parked. Trigger for review/dedupe RDR seeds.

Use to ship a batch of katas selected by ids, priority, parent, or label. Orders the wave, runs scope review by default, then invokes kata-ship per kata. Trigger for ship all/label/priority katas or $kata-flight.

Shared reference for worktree isolation, roborev refine, squash, and fast-forward merge used by ship skills. Not invoked directly; read when kata-ship, prompt-ship, or related skills cite it.

Use to run one pre-lock lens and resolve its findings in the same pass. Lenses: grounding, 3amigo, critique, repeatability, cove. Trigger for pre-lock review, $rdr-prelock, or /rdr-prelock.

Use to close open spikes and round-disturbed assumptions before lock. Runs Stage 6 and routes back if evidence refutes the draft. Trigger for reconcile RDR, $rdr-reconcile, or /rdr-reconcile.

Use to find the current stage and next command for an RDR. Read-only navigator over status, evidence, and artifacts. Trigger for where is RDR, next RDR step, $rdr-status, or /rdr-status.

Use to implement a locked Final RDR into working, spec-verified code. Runs Stage 8 via the launch prompt and is re-entrant from status.md. Trigger for implement RDR, $rdr-implement, or /rdr-implement.

Use to verify an RDR setup. Read-only health check for the seam, five-var contract, engine layout, evidence root, and skill links. Trigger for diagnose RDR, check RDR setup, $rdr-doctor, or /rdr-doctor.

Use to reconcile drift across related Final, unimplemented RDRs before any implement. Runs Stage 7.1 whole-set critique and pairwise contradiction scan. Trigger for cluster reconcile, $rdr-cluster-reconcile, or /rdr-cluster-reconcile.

Use to verify critical RDR assumptions against source, spikes, prior art, and reuse audits. Runs Stage 4 before pre-lock review. Trigger for resolve assumptions, $rdr-resolve, or /rdr-resolve.

Use to run the Finalization Gate and lock an RDR to Final. Runs Stage 7: mechanical sweep plus written gate responses. Trigger for finalize/lock RDR, $rdr-finalize, or /rdr-finalize.

Dual-index corpus management for combined semantic and full-text search. Use when user mentions corpus, dual indexing, syncing content to both Qdrant and MeiliSearch, checking parity between systems, deleting corpora, or managing content that needs both search types.

Search indexed corpora using semantic (vector) OR full-text (keyword) search via the arc CLI. Use when the user asks to search, find, look up, or query a corpus, collection, knowledge base, codebase, docs, PDFs, or markdown. Covers both conceptual queries and exact-term lookups.

Qdrant collection management for semantic search. Use when user mentions managing collections, creating collection, listing collections, verifying collection integrity, exporting or importing collections, or viewing indexed items in Qdrant.

Docker container management for Qdrant and MeiliSearch services. Use when user mentions starting services, stopping services, checking container status, viewing logs, restarting containers, or resetting database services.

MeiliSearch index management for full-text search. Use when user mentions managing indexes, creating index, listing indexes, verifying index health, exporting or importing indexes, or viewing indexed items in MeiliSearch.