/dr-auto
Autonomous-execution meta-command — runs the full pipeline end-to-end with the FB-1..8 rules, the L1 Inline Resolution Rule, and the Question Suppression Ladder turned on by default.
Overview
/dr-auto is the autonomous-execution meta-command introduced in Datarim v2.19.0+. It activates the eight FB-rules (FB-1 through FB-8 — see the Autonomous Agent Operating Rules in your ecosystem CLAUDE.md), the L1 Inline Resolution Rule (close small gaps in-line rather than asking the operator), and the autonomous-ops scope by default through the environment variable DATARIM_AUTO_MODE=1 + the marker file datarim/.auto-mode-active.
The five-level Question Suppression Ladder (L1 inline pattern match → L2 PRD / plan / creative lookup → L3 backlog / archive grep → L4 specific feedback memory → L5 ask the operator) suppresses pipeline clarification questions wherever the answer can be derived deterministically from existing artefacts. L1 Class A gaps close in-line and append to datarim/tasks/{TASK-ID}-auto-inline-log.md. Hard-gated actions (production deploys, secret rotation, force-push to main, public messages on social channels) still escalate to the operator through Ladder L5.
Two modes
- Continue mode —
/dr-auto {TASK-ID}resumes a known task from its last checkpoint and runs it end-to-end through whatever pipeline stages remain. - Bootstrap mode —
/dr-auto "<free-text brief>"kicks off a fresh task from a free-text operator brief, runs/dr-initthen routes through the appropriate pipeline (L1 through L4) without further per-step prompts.
Usage
# Continue: resume the named task from its last checkpoint
/dr-auto TUNE-0327
# Bootstrap: kick off a fresh L1..L4 task end-to-end
/dr-auto "Bump skill count on home page after TUNE-0304 migration"
Canonical contract
The full contract — Ladder definitions, FB-rule enforcement points, hard-gated action list, the L1 Inline Resolution Rule decision tree, and the auto-inline-log schema — lives in skills/autonomous-mode/SKILL.md. Stage-specific suppression hooks are documented per-command (for example, /dr-do TDD red→green transitions resolve through Ladder L1 before L5).
Reversible vs irreversible
Reversible actions proceed automatically (file edits, local test runs, branch creation, Git commits, push to a feature branch, internal documentation updates). Irreversible or public actions remain hard-gated and ask the operator regardless of DATARIM_AUTO_MODE: production deploys, secret rotation, force-push to main, public messages on Telegram / Facebook / LinkedIn / X / VK / Reddit, GitHub release publication on the main org, payment-related operations.