Overview

Create dt-handoff-implementation-space.prompt.md — the Implementation Space exit handoff prompt. This is the final and richest handoff in the DT process. When a user completes Methods 7-9 (Hi-Fi Prototypes → Testing → Iteration at Scale) and is ready to transition to full production implementation, this prompt generates an RPI-ready artifact carrying forward the complete implementation specification, prototype data, testing results, deployment plan, and organizational readiness assessment. The target is task-planner or task-implementor.

Target File

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

Frontmatter

---
description: 'Implementation Space exit handoff — produces RPI-ready prompt from DT implementation validation work'
mode: 'agent'
tools: ['read_file', 'create_file']
---

Required Content

Handoff Context

The Implementation Space exit carries the richest artifact set in the DT process:

• Functional prototype reference: Architecture notes, technical decisions, and specification drafts from Method 7
• Testing evidence: Test protocols, results analysis, and decision logs from Method 8 — including what was validated and what triggered iteration loops
• Iteration history: Refinement log and re-test results from Method 9 — shows what changed and why
• Deployment plan: Organizational deployment plan with change management, training, and adoption metrics from Method 9
• Scaling assessment: Technical, user, and process scaling analysis
• Cumulative D/F/V status: Final state of desirability/feasibility/viability across the full DT cycle
• Complete handoff lineage: References to Problem Space and Solution Space exit artifacts (if they were generated during earlier transitions)

Target Routing

The prompt determines the appropriate RPI entry point:

• → task-planner: When the solution needs production architecture planning — the DT prototype is functional but needs reimplementation for production scale. The generated prompt pre-loads the planner with architecture notes, scaling requirements, and deployment constraints.
• → task-implementor: When the solution is close enough to production that implementation can begin directly — the DT prototype's architecture is suitable for production with refinements. The generated prompt pre-loads the implementor with specifications, technical decisions, and testing evidence.

Tiered Exit Schema

Follow the handoff contract (#583) tiered exit schema:

• Tier 1 (Guided): Early graduation — functional prototype and key learnings, significant production gaps remain
• Tier 2 (Structured): Standard graduation — tested prototype, deployment plan, and clear production gap analysis
• Tier 3 (Comprehensive): Deep graduation — complete artifact set with iteration history, scaling assessment, organizational readiness, and explicit production recommendations

The Implementation Space typically produces Tier 2 or Tier 3 handoffs given the maturity of the work.

Validated-vs-Unknown Markers

The generated artifact explicitly marks:

• [VALIDATED] — Claims backed by Method 8 testing evidence and Method 9 re-testing
• [ASSUMED] — Claims from the DT process not yet tested at production scale
• [UNKNOWN] — Open questions requiring production-phase investigation (scaling behavior, long-term adoption, edge cases not yet tested)

Required Steps

1. Step 1: Read Coaching State — Load coaching state to confirm Implementation Space completion (Methods 7-9).
2. Step 2: Compile DT Artifacts — Read Method 7-9 output directories:
   • Method 7: architecture notes, technical decisions, specification drafts
   • Method 8: test protocols, results analysis, decision logs, iteration triggers
   • Method 9: refinement logs, re-test results, deployment plans, scaling assessments
3. Step 3: Readiness Assessment — Validate artifact completeness against the Implementation 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:
   • Functional prototype specification (from Method 7)
   • Testing evidence and validated/invalidated assumptions (from Method 8)
   • Iteration history and refinement decisions (from Method 9)
   • Deployment plan with change management and adoption metrics
   • Complete handoff lineage referencing earlier exit artifacts
   • 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-implementation-space.md that task-planner or task-implementor can consume directly as context.
6. Step 6: Completion Ceremony — Generate a brief DT cycle completion summary recapping the journey from scope to deployment, key insights, non-linear loops taken, and expectations for the RPI pipeline phase ahead.

Content Sanitization

The handoff artifact must:

• Remove internal coaching metadata not relevant to the RPI consumer
• Convert DT-specific terminology to RPI-understandable language where possible
• Preserve validated/assumed/unknown markers verbatim
• Include only actionable information — omit process notes and facilitator commentary
• Retain handoff lineage references for traceability across DT exit points

Completion Ceremony

The Implementation Space exit marks the end of a full DT cycle. The prompt includes a brief completion summary that:

• Recaps the DT journey from scope to deployment
• Highlights key insights that emerged through the process
• Notes any DT methods that were revisited (non-linear loops) and why
• Sets expectations for the RPI pipeline phase ahead

Token Budget

Target: ~1,000-1,500 tokens for the prompt template. Generated output is the largest of all handoff prompts due to artifact richness.

How to Build This File

This is a .prompt.md file — use the prompt-builder agent (not task-implementor) for the authoring phase. The prompt-builder includes built-in Prompt Quality Criteria validation and sandbox testing specific to AI artifacts (.instructions.md, .prompt.md, .agent.md, SKILL.md).

Workflow: /task-research → /task-plan → /prompt-build → /task-review
Between each phase, run /clear to reset context.

Phase 1: Research

Gather source material for the Implementation Space handoff prompt.

Source Material:

1. design-thinking-for-hve-capabilities/.github/chatmodes/design-thinking.chatmode.md (handoff patterns)
2. design-thinking-for-hve-capabilities/guidance/07-high-fidelity-prototypes.md
3. design-thinking-for-hve-capabilities/guidance/08-user-testing.md
4. design-thinking-for-hve-capabilities/guidance/09-iteration-at-scale.md

These files live in the DT4HVE repository. If you don't have local access, ask the user to provide them or use read_file if the repo is cloned nearby.

Steps:

1. Read all source materials above.
2. Read .github/instructions/prompt-builder.instructions.md for authoring standards.
3. Read any existing dt-handoff-* prompt files for structural precedent (especially the Solution Space handoff).
4. Gather content on Implementation Space exit patterns, production transition approaches, and the complete handoff lineage concept from the cumulative research.

Starter prompt:

/task-research

Research for dt-handoff-implementation-space.prompt.md

Read the DT4HVE source materials:
- design-thinking-for-hve-capabilities/.github/chatmodes/design-thinking.chatmode.md (handoff patterns and routing logic)
- design-thinking-for-hve-capabilities/guidance/07-high-fidelity-prototypes.md
- design-thinking-for-hve-capabilities/guidance/08-user-testing.md
- design-thinking-for-hve-capabilities/guidance/09-iteration-at-scale.md

Extract:
- Implementation Space exit patterns — what signals readiness to leave Method 7/8/9
- Production transition approaches — how DT artifacts convert to production-ready engineering inputs
- Complete handoff lineage concept — tracing from Problem Space through Solution Space to final handoff
- Tiered exit schema for the Implementation Space (which tier routes where)
- Completion ceremony patterns — how to mark a DT journey as complete
- Artifact types carried forward: functional prototypes, testing evidence, iteration history, deployment plans, scaling assessments

Also read .github/instructions/prompt-builder.instructions.md for authoring standards and any existing dt-handoff-*.prompt.md files for structural precedent.

Output: research summary from Phase 1 above

Phase 2: Plan

Plan the prompt structure and routing logic using the research output.

Steps:

1. Review the research output from Phase 1.
2. Plan the handoff prompt — context compilation strategy, target routing logic, tiered exit schema integration, completion ceremony, state update behavior.
3. Define section ordering, token allocation, and confirm mode/tools frontmatter.

Starter prompt:

/task-plan

Plan for dt-handoff-implementation-space.prompt.md

Using the Phase 1 research output, plan the handoff prompt:

- Handoff context compilation — which DT artifacts from Methods 7-9 feed into the prompt, plus lineage from earlier spaces
- Target routing logic — how the prompt decides whether to route to task-planner (needs production architecture) or task-implementor (ready for implementation)
- Tiered exit schema integration — maturity tiers and their routing destinations
- Completion ceremony — how the prompt marks a DT journey as meaningfully concluded
- State update behavior — how the prompt updates DT session state on final handoff
- Prompt mode: agent with tools read_file and create_file
- This is the richest handoff — ensure it carries forward all relevant DT artifacts while remaining usable as an RPI input
- Token budget allocation (~1,000-1,500 tokens for the template)

Output: plan at .copilot-tracking/plans/{date}-dt-handoff-implementation-space-plan.md

Phase 3: Build

Author the prompt file using the prompt-builder agent.

Steps:

1. Review the plan from Phase 2.
2. Author the prompt file using /prompt-build.
3. This is the final DT handoff — it should carry the full artifact lineage and feel like a meaningful transition.

Starter prompt:

/prompt-build file=.github/prompts/dt-handoff-implementation-space.prompt.md

Build using the plan at .copilot-tracking/plans/{date}-dt-handoff-implementation-space-plan.md.

This is the final handoff prompt file for the Implementation Space. Key authoring notes:
- Frontmatter: mode: agent, tools: ['read_file', 'create_file']
- The prompt reads DT artifacts (functional prototypes, testing evidence, iteration history, deployment plans, scaling assessments) and produces a complete RPI-ready prompt file
- Routing logic based on tiered exit schema — routes to task-planner for production architecture needs or task-implementor for implementation-ready work
- Completion ceremony — marks the DT journey as complete with a meaningful transition
- Full artifact lineage — traces from Problem Space through Solution Space to this final handoff
- State update behavior — updates DT session state on final handoff
- This is the richest handoff — carries forward all relevant DT artifacts while remaining usable as an RPI input
- Output must be immediately usable as an RPI input — not a summary or checklist
- Token budget: ~1,000-1,500 tokens for the template

Phase 4: Review

Validate the prompt file against the plan and prompt-builder standards.

Steps:

1. Review the built file against prompt-builder standards and the issue requirements.
2. Validate handoff completeness, routing logic accuracy, tiered schema compliance, completion ceremony quality, and prompt-builder standards.

Starter prompt:

/task-review

Review .github/prompts/dt-handoff-implementation-space.prompt.md

Validate against:
- prompt-builder.instructions.md authoring standards
- Handoff completeness — all Implementation Space artifacts carried forward, plus lineage from earlier spaces
- Routing logic accuracy — correct tiered exit schema with appropriate destinations
- Tiered schema compliance — maturity tiers match the handoff contract
- Completion ceremony quality — the final handoff feels like a meaningful transition, not just a data dump
- State update behavior — session state is updated on final handoff
- Frontmatter specifies mode: agent and tools: ['read_file', 'create_file']
- Output is a complete RPI-ready prompt file, not just a summary
- Token budget: ~1,000-1,500 tokens

Authoring Standards

Follow .github/instructions/prompt-builder.instructions.md:

• Mode: agent (needs read_file to compile DT artifacts)
• Prompt produces a .prompt.md file as output
• Handoff contract compliance is mandatory
• This is the final DT handoff — it should feel like a meaningful transition

Success Criteria

• File created at .github/prompts/dt-handoff-implementation-space.prompt.md
• Frontmatter specifies mode: 'agent' and tools: ['read_file', 'create_file']
• Carries forward functional prototype, testing evidence, iteration history, deployment plan, and scaling assessment
• Routes to task-planner (needs production architecture) or task-implementor (ready for implementation) based on maturity
• Implements tiered exit schema from the handoff contract
• Applies validated-vs-unknown markers with production-scale awareness
• Includes completion ceremony recapping the DT journey
• References handoff lineage when earlier exit artifacts exist
• Updates coaching state to reflect full DT cycle completion
• Token count within ~1,000-1,500 for the prompt template
• 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