The /dr-continue Command — Deprecated Alias for /dr-next
Why /dr-continue still works, what it actually does when invoked, and why all new work should use /dr-next instead.
Read more →Articles, tutorials, and announcements
Why /dr-continue still works, what it actually does when invoked, and why all new work should use /dr-next instead.
Read more →How /dr-plugin manages opt-in extensions for Datarim: the two-manifest architecture, datarim-core bootstrap, symlink-based installation, and the phased roadmap for enable/disable and rollback.
Read more →What /dr-help shows: the full pipeline, all command categories, the complexity routing table, the agent roster, and backlog navigation — in one place.
Read more →How /humanize scans for AI writing patterns across vocabulary, structure, and rhythm, then surgically removes them while keeping the author's message and voice intact.
Read more →How /factcheck extracts every verifiable claim from a draft, verifies each against authoritative sources, and delivers a corrected document with the author's voice intact.
Read more →How /dr-publish adapts content for each target platform, runs pre-publish checks, and produces ready-to-send payloads — without reformatting by hand.
Read more →How /dr-write activates the Writer agent to plan, draft, and hand off content — from blog posts to technical docs — with a built-in quality pipeline.
Read more →How /dr-edit runs three distinct editorial phases — fact verification, AI pattern removal, and structural polish — before any piece of content goes live.
Read more →How /dr-addskill researches best practices, audits existing components, and generates new skills, agents, and commands for Datarim — with a TDD pass and a stack-agnostic gate before anything is written.
Read more →How /dr-optimize detects bloat, unused components, duplicate coverage, and broken references across Datarim skills, agents, and commands — then proposes and applies fixes with an explicit approval gate.
Read more →