/dr-wizard

Overview

/dr-wizard turns a rough brief into a structured task specification before /dr-prd. It asks one focused question at a time, records each answer, and builds a knowledge and dependency graph alongside the interview. The wizard can pause and resume without a manual session identifier because its state is anchored to the task ID.

When to Use It

• The goal is clear, but important requirements or constraints are still implicit.
• A hard question needs a short side interview before returning to the main thread.
• An architectural choice would benefit from an on-demand consilium panel.
• The scope may change during discovery and downstream research or planning must be marked stale.

Interview Flow

1. Resume or start. The wizard checks for existing task state and replays it instead of restarting.
2. Ask one question. Each question and answer is appended to the task interview log.
3. Drill when needed. A nested side-thread captures references to relevant earlier answers, then writes its conclusion back to the parent question.
4. Record decisions. Requirements, concepts, and decisions become graph nodes connected by dependency, refinement, or resolution edges.
5. Finalize and validate. The wizard closes open drill frames, validates the event log and graph, and emits a requirements summary for /dr-prd.

Persisted Artefacts

datarim/wizard/<TASK-ID>.wizard.jsonl  # append-only interview events
datarim/wizard/<TASK-ID>.graph.jsonl   # concepts, requirements, decisions

Only a finalized and validated wizard artefact is authoritative. An interrupted interview remains resumable but is not consumed as a completed specification.

Re-scope and Autonomy

A changed requirement marks research, planning, or both as dirty. The wizard reports those flags; it does not silently launch a new planning cycle. In autonomous mode it resolves answerable questions from available context and can convene a consilium for difficult decisions, while the same hard-gated action boundary remains in force.

Next Step

After finalization, run /dr-prd <TASK-ID>. The PRD stage consumes the completed requirements summary and graph instead of repeating the discovery interview.