feat(instructions): add DT-aware task-implementor context instructions

.github/instructions/design-thinking/dt-rpi-implement-context.instructions.md

@@ -0,0 +1,46 @@
+---
+description: 'DT-aware task-implementor context: fidelity constraints, stakeholder validation, and iteration support'
+applyTo: '**/.copilot-tracking/dt/**'
+---
+
+# DT Implementation Context
+
+When task-implementor operates on DT artifacts or executes a DT-originated plan, these adjustments augment standard implementation behavior. The plan originates from a Design Thinking process, so fidelity constraints, stakeholder validation, and iteration support shape implementation decisions.
+
+## Implementation Adjustments
+
+| Standard Implementation      | DT-Informed Implementation                                                       |
+|------------------------------|----------------------------------------------------------------------------------|
+| Production-quality code      | Space-appropriate fidelity (rough/scrappy/functional)                            |
+| Complete feature delivery    | Constraint-validated scope matching DT prototype specifications                  |
+| Technical correctness focus  | Stakeholder experience validation alongside technical correctness                |
+| Forward-only execution       | Iteration-aware execution with return paths to earlier DT methods                |
+| Full polish and optimization | Anti-polish: functional core without premature optimization or visual refinement |
+
+## DT-Specific Implementation Patterns
+
+* Enforce fidelity constraints from the originating DT space. Problem Space outputs are research-grade, Solution Space outputs are scrappy and concept-grade, and Implementation Space outputs are functionally rigorous without visual polish.
+* Verify implementation against each stakeholder group from the handoff's stakeholder map (an artifact of type `stakeholder-map` in the handoff `artifacts` array). When the handoff contains no stakeholder map artifact, flag this gap before proceeding.
+* Reference DT artifact paths (`.copilot-tracking/dt/{project-slug}/`) in implementation comments and change logs so decisions trace back to research and synthesis outputs.
+* Treat handoff items marked `assumed` with explicit verification steps during implementation. Items marked `unknown` or `conflicting` require resolution before the affected implementation proceeds.
+* Support return paths to earlier DT methods as conditional outcomes within phase completion criteria rather than treating all implementation as forward-only.
+* For Solution Space implementations, enforce anti-polish: scope deliverables to scrappy fidelity and flag production-quality requests as out-of-scope for the current space.
+
+## Fidelity Constraints by DT Space
+
+| Originating Space                  | Implementation Fidelity                                                             |
+|------------------------------------|-------------------------------------------------------------------------------------|
+| Problem Space (Methods 1-3)        | Research-grade: outputs serve understanding, not production deployment              |
+| Solution Space (Methods 4-6)       | Concept-grade: scrappy prototypes, paper-level fidelity, no production optimization |
+| Implementation Space (Methods 7-9) | Functionally rigorous: working systems with real data, not visual polish            |
+
+## Return Path Triggers
+
+Recommend returning to DT coaching rather than continuing implementation when any of these conditions emerge:
+
+* Implementation reveals that core assumptions validated during DT coaching do not hold under real-world constraints.
+* Stakeholder groups absent from the original stakeholder map surface during implementation.
+* Fidelity requirements for the deliverable exceed the originating space tier, indicating the team may have advanced too quickly through DT methods.
+* The prototype or concept validated during DT coaching fails under implementation constraints, requiring a return to Solution Space methods for redesign.
+
+These adjustments complement co-loaded instruction files (`dt-rpi-handoff-contract`, `dt-quality-constraints`, `dt-method-sequencing`, `dt-rpi-planning-context`, `dt-rpi-review-context`): reference their content during implementation rather than duplicating it.

collections/design-thinking.collection.md

@@ -28,6 +28,7 @@ This collection includes agents, prompts, and instructions for:
 - **DT Method 04 Deep: Advanced Brainstorming Techniques** — Advanced facilitation techniques (brainwriting, morphological analysis, provocation), creative block recovery, convergence frameworks (impact/effort matrix, weighted D/F/V scoring), and cross-pollination from analogous industries loaded on-demand for complex Method 4 coaching scenarios
 - **DT Industry: Healthcare** — Healthcare-specific vocabulary mapping, constraints (HIPAA, patient safety, clinical workflow), empathy tools (patient journey mapping, clinician shadow), and an ED wait-time reference scenario for on-demand industry context loading
 - **DT→RPI Handoff Contract** — Exit-point definitions, artifact schemas, per-agent input contracts, graduation awareness behavior, and quality markers for lateral transitions from Design Thinking coaching into the RPI workflow
+- **DT RPI Implementation Context** — DT-aware task-implementor augmentation that enforces space-appropriate fidelity constraints, stakeholder validation against handoff maps, confidence-marker handling, and return path triggers when operating on DT artifacts
 - **DT RPI Planning Context** — DT-aware task-planner augmentation that shapes implementation planning around fidelity constraints, iteration support, confidence-informed risk assessment, and stakeholder-segmented success criteria when operating on DT artifacts
 - **DT RPI Research Context** — DT-aware task-researcher augmentation that frames research around stakeholder needs, quality-marked findings, assumption validation, and return path triggers when operating on DT artifacts
 - **DT RPI Review Context** — DT-aware task-reviewer augmentation that defines quality criteria per artifact type (coaching, method, deep, industry, handoff, agent, output), review checklist additions for coaching tone and fidelity enforcement, anti-patterns to flag, and severity mapping for Design Thinking artifacts

collections/design-thinking.collection.yml

@@ -85,6 +85,9 @@ items:
   - path: .github/instructions/design-thinking/dt-rpi-handoff-contract.instructions.md
     kind: instruction
     maturity: experimental
+  - path: .github/instructions/design-thinking/dt-rpi-implement-context.instructions.md
+    kind: instruction
+    maturity: experimental
   - path: .github/instructions/design-thinking/dt-rpi-planning-context.instructions.md
     kind: instruction
     maturity: experimental

collections/hve-core-all.collection.yml

@@ -300,6 +300,9 @@ items:
 - path: .github/instructions/design-thinking/dt-rpi-handoff-contract.instructions.md
   kind: instruction
   maturity: experimental
+- path: .github/instructions/design-thinking/dt-rpi-implement-context.instructions.md
+  kind: instruction
+  maturity: experimental
 - path: .github/instructions/design-thinking/dt-rpi-planning-context.instructions.md
   kind: instruction
   maturity: experimental

plugins/design-thinking/README.md

@@ -49,6 +49,7 @@ copilot plugin install design-thinking@hve-core
 | dt-coaching-state                    | Coaching state schema for Design Thinking session persistence, method progress tracking, and session recovery                                                                                                                              |
 | dt-industry-healthcare               | Healthcare industry context for DT coaching — vocabulary, constraints, empathy tools, and reference scenarios                                                                                                                              |
 | dt-rpi-handoff-contract              | DT-to-RPI handoff contract defining exit points, artifact schemas, and per-agent input requirements for lateral transitions from Design Thinking to RPI workflow                                                                           |
+| dt-rpi-implement-context             | DT-aware task-implementor context: fidelity constraints, stakeholder validation, and iteration support                                                                                                                                     |
 | dt-rpi-planning-context              | DT-aware task-planner context: fidelity constraints, iteration support, and confidence-informed planning for DT artifacts                                                                                                                  |
 | dt-rpi-research-context              | DT-aware task-researcher context — frames research around DT methods, stakeholder needs, and empathy-driven inquiry                                                                                                                        |
 | dt-rpi-review-context                | DT-aware task-reviewer context: quality criteria for Design Thinking artifacts                                                                                                                                                             |

plugins/design-thinking/instructions/dt-rpi-implement-context.md

@@ -0,0 +1 @@
+../../../.github/instructions/design-thinking/dt-rpi-implement-context.instructions.md

plugins/hve-core-all/README.md

@@ -145,6 +145,7 @@ copilot plugin install hve-core-all@hve-core
 | dt-method-sequencing                 | Method transition rules, nine-method sequence, space boundaries, and non-linear iteration support for Design Thinking coaching                                                                                                                              |
 | dt-quality-constraints               | Quality constraints, fidelity rules, and output standards for Design Thinking coaching across all nine methods                                                                                                                                              |
 | dt-rpi-handoff-contract              | DT-to-RPI handoff contract defining exit points, artifact schemas, and per-agent input requirements for lateral transitions from Design Thinking to RPI workflow                                                                                            |
+| dt-rpi-implement-context             | DT-aware task-implementor context: fidelity constraints, stakeholder validation, and iteration support                                                                                                                                                      |
 | dt-rpi-planning-context              | DT-aware task-planner context: fidelity constraints, iteration support, and confidence-informed planning for DT artifacts                                                                                                                                   |
 | dt-rpi-research-context              | DT-aware task-researcher context — frames research around DT methods, stakeholder needs, and empathy-driven inquiry                                                                                                                                         |
 | dt-rpi-review-context                | DT-aware task-reviewer context: quality criteria for Design Thinking artifacts                                                                                                                                                                              |

plugins/hve-core-all/instructions/dt-rpi-implement-context.md

@@ -0,0 +1 @@
+../../../.github/instructions/design-thinking/dt-rpi-implement-context.instructions.md