dt-rpi-integration

Create a handoff summary file recording the exit point, artifacts, constraints, and assumptions with confidence markers, then target rpi-research as the entry phase. All DT exits enter at rpi-research regardless of maturity; later phases consume context through the research output.

Three exit points align with DT space boundaries: Problem Statement Complete (Methods 1-3), Concept Validated (Methods 4-6), and Implementation Spec Ready (Methods 7-9). Each tier describes artifact richness, not which RPI phase to skip.

Validated items are confirmed through multiple sources and accepted as grounded input. Assumed items need verification during research, unknown items become primary research targets, and conflicting items must be resolved before planning proceeds.

Return when core assumptions are invalidated, new stakeholder groups surface, fidelity requirements exceed the originating space tier, or validated concepts fail under implementation constraints. Return paths are modeled as conditional outcomes in plan completion criteria.

Use a stick-figure template with all five required layers: stick figures, minimal lines, plain white background, black-and-white line art, and no shading. Describe one core interaction per concept and avoid terms like detailed, polished, or interface mockup.

All DT coaching artifacts are scoped to .copilot-tracking/dt/{project-slug}/ directories. Artifacts must never be written directly under .copilot-tracking/dt/ without a project-slug directory.