Overview

Create dt-handoff-problem-space.prompt.md — the Problem Space exit handoff prompt invoked when a user graduates from Methods 1-3 and chooses to hand off to the RPI pipeline. This prompt reads DT coaching artifacts, compiles them into the exit-point schema defined in the handoff contract (#583), and produces an RPI-ready prompt file targeting task-researcher.

Target File

.github/prompts/dt-handoff-problem-space.prompt.md

Frontmatter

---
description: 'Problem Space exit handoff — compiles DT Methods 1-3 outputs into RPI-ready artifact targeting task-researcher'
mode: 'agent'
tools: ['read_file', 'create_file']
---

Required Steps

1. Step 1: Read Coaching State — Load coaching state to confirm Problem Space completion (Methods 1-3).
2. Step 2: Compile DT Artifacts — Read Method 1-3 output directories:
   • Method 1: stakeholder-map.md, scope-boundaries.md, assumptions-log.md
   • Method 2: research-plan.md, raw-findings.md, interview-notes/
   • Method 3: affinity-clusters.md, insight-statements.md, problem-definition.md, hmw-questions.md
3. Step 3: Readiness Assessment — Validate artifact completeness against the Problem Space exit schema from the handoff contract. Flag gaps and ask user whether to proceed or return to address them.
4. Step 4: Produce Handoff Artifact — Generate the exit-point artifact with:
   • Validated problem statement (from Method 3)
   • Stakeholder map summary (from Method 1)
   • Research themes and key insights (from Methods 2-3)
   • Gap analysis with validated/assumed/unknown markers
   • Coaching context notes for the receiving RPI agent
5. Step 5: Generate RPI Entry — Create a structured handoff document at .copilot-tracking/dt/{project-slug}/rpi-handoff-problem-space.md that task-researcher can consume directly as context. This is a data document (not an executable prompt), so it uses the .md extension rather than .prompt.md.

Content Sanitization

Per backlog planning instructions, the handoff artifact must:

• Use no .copilot-tracking/ paths in the generated prompt body (reference content inline)
• Include no planning reference IDs
• Produce clean, self-contained context for the receiving RPI agent

Handoff Quality Markers

Each compiled artifact section includes quality markers:

• Validated: Evidence from research supports this claim
• Assumed: Coach/user believes this but hasn't tested it
• Unknown: Identified as a gap requiring RPI investigation
• Conflicting: Multiple sources disagree — RPI should investigate

RPI Pipeline Workflow

1. task-researcher: Gather DT4HVE exit handoff patterns, RPI entry prompt conventions, and handoff contract schema for Problem Space exit.
2. task-planner: Plan the prompt — steps, artifact compilation logic, readiness assessment criteria, output format.
3. task-implementor: Author following prompt-builder standards. The generated RPI entry prompt must be self-contained.
4. task-reviewer: Validate step protocol, artifact compilation completeness, content sanitization, handoff quality markers, prompt-builder compliance.

Success Criteria

• Prompt file created at .github/prompts/dt-handoff-problem-space.prompt.md
• Step-based protocol with 5 steps
• Reads all Method 1-3 artifact directories
• Readiness assessment validates against Problem Space exit schema
• Handoff artifact includes quality markers (validated/assumed/unknown/conflicting)
• Generated RPI entry prompt is self-contained (no .copilot-tracking/ path references)
• Targets task-researcher as the receiving RPI agent
• Ends with --- separator and activation
• Passes task-reviewer validation against prompt-builder standards
• Each prompt, instructions, or agent file registered in collections/design-thinking.collection.yml with path and kind fields
• Each prompt, instructions, or agent file registered in collections/hve-core-all.collection.yml with path and kind fields
• npm run plugin:generate succeeds after collection manifest updates