The dr-next-snapshot-replay Skill — Stage Snapshot Consumer Contract
How /dr-next reads a stage snapshot, validates it, assembles the resume prompt, and routes to the right next command — without re-reading the full task history.
Read more →Articles, tutorials, and announcements
How /dr-next reads a stage snapshot, validates it, assembles the resume prompt, and routes to the right next command — without re-reading the full task history.
Read more →How Datarim detects and resolves task-ID conflicts that occur when two parallel sessions reserve the same identifier in the window between /dr-init and /dr-archive.
Read more →/dr-spec is retired. The same graph validator that traced every requirement to its evidence now runs automatically inside /dr-prd, /dr-plan, /dr-do, /dr-qa, and /dr-compliance — no extra step, no separate invocation.
Read more →A short note on a deprecated skill alias and where its consumer contract moved.
Read more →How the dispatching-parallel-agents skill eliminates sequential investigation of independent failures by dispatching isolated agents to each problem domain simultaneously and integrating their results.
Read more →How the discovery skill structures requirements gathering as a one-question-at-a-time interview where every question comes with a proposed answer — making the process faster and reducing ambiguity before implementation starts.
Read more →How the diataxis-docs skill enforces the Diátaxis taxonomy across every Datarim-managed repo, mapping every documentation type to one of four orthogonal categories and blocking the anti-patterns that erode it over time.
Read more →A look at the datarim-system skill — the always-loaded ruleset that defines where Datarim state lives, how task files are structured, and how agents resolve paths and load order.
Read more →How the datarim-doctor skill defines a thin one-liner contract for Datarim's operational indexes and runs an 8-pass migration to enforce it without losing a single task record.
Read more →How the cta-format skill enforces a structured "Next Step" block at the end of every pipeline command, eliminating the mental load of mapping task IDs to the next action.
Read more →