Skip to main content

In this article

Tutorial: Handing Off from DT to RPI

Prerequisites​

Before starting a handoff, ensure you have:

  • A DT Coach session with a project slug, such as factory-floor-maintenance
  • Completed Methods 7-9 for the Implementation Spec Ready exit
  • A coaching state file at .copilot-tracking/dt/{project-slug}/coaching-state.md
  • A project folder at .copilot-tracking/dt/{project-slug}/
  • Familiarity with RPI workflow basics

NOTE

This tutorial continues the manufacturing scenario from Using DT Methods Together. The team discovered that the plant manager's "quality dashboard" request actually reflects a knowledge-loss problem across shifts.

Implementation Spec Ready Handoff​

The DT-to-RPI handoff can occur at three exit points: Problem Statement Complete (Methods 1-3), Concept Validated (Methods 4-6), and Implementation Spec Ready (Methods 7-9). Every exit enters the RPI pipeline through rpi-research, and later exits seed the Research phase with progressively richer context. This tutorial walks through the Implementation Spec Ready exit, which hands off the richest artifact set after Methods 7-9 are complete. The same steps apply to the earlier exits with leaner artifacts.

What the Handoff Includes​

The handoff artifact carries the richer DT evidence you gathered through the Implementation Space:

  • Architecture decisions and technical trade-offs
  • High-fidelity prototype outcomes and test evidence
  • Stakeholder and constraint context from earlier methods
  • Confidence markers for each artifact, constraint, and assumption

When you review the handoff before activating rpi-research, pay attention to items marked assumed, unknown, or conflicting. Those items become research targets for the incoming RPI work.

Step 1: Confirm Readiness with DT Coach​

After completing Method 9, ask the coach to assess readiness:

We've finished Method 9. Assess where we are and recommend the next step.

The coach reviews the completed Implementation Space work and confirms that the handoff is ready for rpi-research.

Step 2: Generate the Handoff Artifact​

In the same DT Coach session, ask the coach to package the Implementation Space for RPI:

Prepare the Implementation Space handoff to RPI for project
factory-floor-maintenance.

The coach follows the Implementation Space exit procedure from the dt-rpi-integration skill. Your request counts as the explicit handoff choice. The coach compiles the available DT artifacts, applies the current handoff contract, and produces two files:

  • .copilot-tracking/dt/{project-slug}/handoff-summary-implementation-space.md: The structured handoff metadata with the exit tier and confidence markers
  • .copilot-tracking/research/{project-slug}-research-topic.md: A self-contained document for rpi-research

Step 3: Review the Artifact​

Open .copilot-tracking/research/factory-floor-maintenance-research-topic.md and verify that it includes:

  • A clear problem framing and implementation context
  • Stakeholder context, constraints, and assumptions with confidence markers
  • Evidence from High-Fidelity Prototypes, User Testing, and Iteration at Scale
  • Clear investigation targets for items marked assumed, unknown, or conflicting

Step 4: Hand Off to rpi-research​

Clear your chat context, then invoke the Research phase skill with the path to the generated handoff file:

/clear
/rpi-research Research implementation options for the voice-guided
repair system based on the DT handoff artifact at
.copilot-tracking/research/factory-floor-maintenance-research-topic.md

With the plugin installed in VS Code, the Research skill appears as /hve-core:rpi-research.

rpi-research uses the handoff to:

  • Scope technical research around the validated implementation context
  • Treat assumed items as verification targets
  • Treat unknown items as primary research targets
  • Pass the DT-informed findings into the standard RPI pipeline

Step 5: Continue Through RPI​

After research completes, continue with the standard RPI phases:

/clear → /rpi-plan → /clear → /rpi-implement → /clear → /rpi-review

The research artifact carries the validated DT context into planning and implementation rather than recreating it from scratch.

Each phase ends with a Next Steps section that names the exact command to run next. To have one agent carry the work through the phases instead, select RPI Agent in the agent picker and point it at the research artifact.

When RPI Returns to DT​

The handoff is not one-way. rpi-research can recommend returning to DT coaching when research reveals issues that trace back to DT assumptions. When that happens, open a new DT Coach session, restate the finding that invalidated the assumption, and resume from the earlier method that needs revision.

Quick Reference​

ActionCommand or Step
Check readinessAsk DT Coach to assess readiness and recommend the next step
Generate the implementation handoffAsk DT Coach to prepare the Implementation Space handoff to RPI
Switch to RPI/clear, then run /rpi-research with the path to the handoff artifact
Return to DT from RPISelect DT Coach in the agent picker and describe the finding that triggered the return

🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.