/dr-next

Overview

/dr-next is designed for returning to work after a break or a new session. It reads all context files, determines which pipeline phase you are in, shows a summary of where you left off, and resumes the appropriate action. If multiple tasks are active, it shows all of them with their current phases and asks which one to resume. If there is no active task, it checks the backlog and suggests what to start next.

Usage

/dr-next

What It Does

1. Task Resolution — applies the Task Resolution Rule. If multiple tasks are active, shows all with their current phase and asks which to resume.
2. Snapshot-First Read — if datarim/snapshots/{TASK-ID}.snapshot.md validates, reads it as the primary source of where the task stopped; otherwise falls back to activeContext.md, tasks.md, the task description file, and backlog.md.
3. Determine Phase — identifies the current pipeline stage for the selected task: INIT, PLAN, DESIGN, DO, QA, COMPLIANCE, or ready for archive.
4. Show Context Summary — displays the task, current phase, what has been completed, and what remains.
5. Resume Action — picks up work where you left off:
   • In PLAN phase — continues planning
   • In DO phase — continues implementation from the next unfinished step
   • Ready for ARCHIVE — suggests /dr-archive

Arguments

None.

Multi-Task Routing

When multiple tasks are active, the command displays a numbered list of all tasks with their phases and asks which one to resume. This is the Task Resolution Rule in action — no ambiguity, no silent assumptions.

Routing When No Active Task

If there is no active task, the command checks the backlog:

• If pending items exist — displays them and suggests /dr-init with backlog selection
• If the backlog is empty — suggests /dr-init with a new task description

Example Session

> /dr-next

Restoring context...

Multiple active tasks found:
  1. <TASK-ID> — Implement user authentication (L3, DO phase, 5/8 done)
  2. UI-NNNN — Dashboard dark mode (L2, PLAN phase)

Which task to resume? (1/2)
> 1

=== RESUMING TASK ===
  ID: <TASK-ID>
  Title: Implement user authentication
  Complexity: Level 3
  Phase: DO (implementation)

Last checkpoint:
  Completed: steps 1-5 of 8
  Last activity: auth.middleware.ts — token validation

Remaining work:
  Step 6: Password reset flow
  Step 7: Rate limiting on auth endpoints
  Step 8: Integration tests

Resuming step 6: Password reset flow...

Files Read

• datarim/activeContext.md — current context and phase
• datarim/tasks.md — task details and plan
• datarim/snapshots/{TASK-ID}.snapshot.md — last completed stage (read first when valid)
• datarim/tasks/{TASK-ID}-task-description.md — implementation notes and what has been completed
• datarim/backlog.md — for routing when no active task

Related Commands

• /dr-status — read-only status check without resuming
• /dr-init — start a new task when nothing is active
• /dr-do — the execution stage that /dr-next most often resumes

Reporting the result

Apply Human Outcome Reporting before a human-facing update or result. Explain the user-visible outcome, the original conditions, checks and evidence, and open limitations. A stage result does not mean the entire task is complete. Keep exact protocols and technical records intact. To explain again without continuing work, use /dr-explain.