rein

Runtime-backed Socratic interview with durable state, clarity scoring, and spec bundle output

Run one task through the full REIN flow from clarification through implementation, cleanup, review, and verification

Use before committing. Self-reviews the current diff for unrelated changes, debug leftovers, test weakening, and scope drift.

Run a regression-tests-first cleanup/refactor workflow to reduce slop

Use after triage, before implementation. Breaks complex work into sequenced steps with risks, checkpoints, rollback boundaries, and interview-result handoff support.

Use before ambiguous or multi-file work. Surfaces relevant files, assumptions, success criteria, and cheating boundaries.

Understand a codebase and maintain .rein/codebase/ as a navigable map with evidence-backed findings

Use when requirements are too large, contradictory, or need negotiation. Produces a scope contract with what will and will not be done.

Use after a miss, regression, or suspicious shortcut. Captures what failed and what rule should change.

Use before declaring code work complete. Runs verification, reviews diff hygiene, and emits an evidence report.