Skip to content

Commit 34c7b89

Browse files
chaosdinosaurchaosdinosaur
authored
feat(instructions): create dt-rpi-research-context.instructions.md (#689)
# Pull Request ## Description Create `dt-rpi-research-context.instructions.md` — a DT-aware instruction file that auto-loads when task-researcher operates on DT artifacts (`.copilot-tracking/dt/**`). Augments standard researcher behavior with: - **Research framing adjustments**: Stakeholder impact focus, multi-perspective analysis, quality-marked findings - **DT-specific research patterns**: Assumption validation, gap investigation, empathy data synthesis, industry context integration - **Output format additions**: Assumption validation results, gap resolution, stakeholder impact assessment, DT coach return recommendation - **Return path triggers**: Problem statement revision, new stakeholders, invalidated assumptions, conflicting synthesis evidence ## Related Issue(s) Closes #594 ## Type of Change **AI Artifacts:** - [x] Reviewed contribution with `prompt-builder` agent and addressed all feedback - [x] Copilot instructions (`.github/instructions/*.instructions.md`) ## Sample Prompts (for AI Artifact Contributions) **User Request:** > Research the validated problem statement from the DT coaching handoff **Execution Flow:** 1. Task-researcher activates on files in `.copilot-tracking/dt/` — instructions auto-load 2. Research framing shifts from pure technical to stakeholder-driven, multi-perspective 3. Handoff `assumed` and `unknown` items become investigation targets 4. Output includes assumption validation results, stakeholder impact, and return path recommendation **Output Artifacts:** Standard research document augmented with DT-specific sections (assumption validation results, gap resolution, stakeholder impact assessment, DT coach return recommendation) **Success Indicators:** - Quality markers (validated/assumed/unknown/conflicting) used in findings - Multi-stakeholder perspectives represented - Return path recommendation present when warranted ## Testing - `npm run lint:md` — 0 errors - `npm run lint:frontmatter` — 0 errors - `npm run lint:collections-metadata` — 0 errors (design-thinking: 22 items, hve-core-all: 109 items) - `npm run spell-check` — 0 issues - `npm run plugin:generate` — successful ## Checklist ### Required Checks - [x] Files follow existing naming conventions - [x] Changes are backwards compatible ### AI Artifact Contributions - [x] Verified contribution follows common standards and type-specific requirements ### Required Automated Checks - [x] Markdown linting: `npm run lint:md` - [x] Spell checking: `npm run spell-check` - [x] Frontmatter validation: `npm run lint:frontmatter` ## Security Considerations - [x] This PR does not contain any sensitive or NDA information
1 parent 277963d commit 34c7b89

8 files changed

Lines changed: 53 additions & 0 deletions

File tree

‎.github/instructions/design-thinking/dt-rpi-research-context.instructions.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
description: 'DT-aware task-researcher context — frames research around DT methods, stakeholder needs, and empathy-driven inquiry'
3+
applyTo: '**/.copilot-tracking/dt/**'
4+
---
5+
6+
# DT Research Context
7+
8+
When task-researcher receives a handoff from the DT coach, these adjustments augment standard research behavior. The research question originates from a Design Thinking process rather than a technical spec, so stakeholder perspectives and empathy-driven inquiry shape the research framing.
9+
10+
## Research Framing Adjustments
11+
12+
| Standard Research | DT-Informed Research |
13+
|---------------------------------|-----------------------------------------------------------------|
14+
| Technical feasibility focus | Stakeholder impact and technical feasibility |
15+
| Single-perspective analysis | Multi-stakeholder analysis across roles and contexts |
16+
| Binary findings (works/doesn't) | Quality-marked findings (validated/assumed/unknown/conflicting) |
17+
| Forward-only to planner | May return to DT coach when findings warrant revisiting |
18+
| Code-centric results | Human-centric results with code implications |
19+
20+
## DT-Specific Research Patterns
21+
22+
* When the research question references stakeholders, investigate from each stakeholder perspective identified in the handoff artifact.
23+
* Handoff items marked `assumed` become verification targets — seek evidence that confirms or contradicts each assumption.
24+
* Handoff items marked `unknown` become primary research targets with dedicated investigation.
25+
* Process qualitative data (interview themes, observation patterns) alongside quantitative data from the DT artifact paths.
26+
* When an industry context template was active during coaching, reference its vocabulary mapping and constraint inventory for domain-specific framing.
27+
28+
## Output Format Additions
29+
30+
When producing research output in DT context, include these sections alongside the standard research document:
31+
32+
* For each `assumed` item from the handoff, state whether evidence supports, contradicts, or remains inconclusive in an Assumption Validation Results section.
33+
* For each `unknown` item, provide findings or recommend continued investigation with rationale in a Gap Resolution section.
34+
* Describe how research findings affect each stakeholder group from the handoff's stakeholder map in a Stakeholder Impact Assessment section.
35+
* State whether findings warrant returning to DT coaching before proceeding to planning, with rationale, in a DT Coach Return Recommendation section.
36+
37+
## Return Path Triggers
38+
39+
Recommend returning to DT coaching rather than proceeding to planning when any of these conditions emerge:
40+
41+
* The problem statement requires significant revision based on research findings.
42+
* Research reveals stakeholders not represented in the original stakeholder map.
43+
* Fundamental assumptions from Method 1-3 synthesis are invalidated by evidence.
44+
* Conflicting evidence indicates the Method 3 synthesis needs rework before implementation planning can proceed.

‎collections/design-thinking.collection.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ This collection includes agents, prompts, and instructions for:
1717
- **DT Method 03 Deep** — Advanced affinity analysis with multi-pass clustering, insight frameworks with observation-inference-insight formula, HMW question scaffolding, problem statement articulation, and manufacturing synthesis patterns
1818
- **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
1919
- **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
20+
- **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
2021
- **DT Method 07: High-Fidelity Prototypes** — Technical translation, functional prototypes, and specifications for Implementation Space entry with three-hat architecture and progressive fidelity modeling
2122
- **DT Method 07: Deep Expertise** — On-demand fidelity translation, architecture trade-off analysis, specification writing patterns, and manufacturing-specific prototyping guidance for complex Method 7 coaching scenarios
2223
- **DT Method 08: User Testing** — Evidence-based evaluation, test protocols, and non-linear iteration support for structured user testing of hi-fi prototypes with leap-enabling questioning and loop decision coaching

‎collections/design-thinking.collection.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,8 @@ items:
3838
kind: instruction
3939
- path: .github/instructions/design-thinking/dt-rpi-handoff-contract.instructions.md
4040
kind: instruction
41+
- path: .github/instructions/design-thinking/dt-rpi-research-context.instructions.md
42+
kind: instruction
4143
- path: .github/instructions/design-thinking/dt-method-01-deep.instructions.md
4244
kind: instruction
4345
- path: .github/instructions/design-thinking/dt-method-01-scope.instructions.md

‎collections/hve-core-all.collection.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -222,6 +222,8 @@ items:
222222
kind: instruction
223223
- path: .github/instructions/design-thinking/dt-rpi-handoff-contract.instructions.md
224224
kind: instruction
225+
- path: .github/instructions/design-thinking/dt-rpi-research-context.instructions.md
226+
kind: instruction
225227
- path: .github/instructions/github/community-interaction.instructions.md
226228
kind: instruction
227229
maturity: experimental

‎plugins/design-thinking/README.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,7 @@ copilot plugin install design-thinking@hve-core
3636
| dt-coaching-state | Coaching state schema for Design Thinking session persistence, method progress tracking, and session recovery |
3737
| dt-industry-healthcare | Healthcare industry context for DT coaching — vocabulary, constraints, empathy tools, and reference scenarios |
3838
| 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 |
39+
| dt-rpi-research-context | DT-aware task-researcher context — frames research around DT methods, stakeholder needs, and empathy-driven inquiry |
3940
| dt-method-01-deep | Deep expertise for Method 1: Scope Conversations, covering advanced stakeholder analysis, power dynamics, and scope negotiation |
4041
| dt-method-01-scope | Method 1 Scope Conversations coaching knowledge for Design Thinking: frozen vs fluid assessment, stakeholder discovery, constraint patterns, and conversation navigation |
4142
| dt-method-03-deep | Deep expertise for Method 3: Input Synthesis — advanced affinity analysis, insight frameworks, and problem statement articulation |

‎plugins/design-thinking/instructions/dt-rpi-research-context.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../../.github/instructions/design-thinking/dt-rpi-research-context.instructions.md

‎plugins/hve-core-all/README.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,7 @@ copilot plugin install hve-core-all@hve-core
128128
| dt-method-sequencing | Method transition rules, nine-method sequence, space boundaries, and non-linear iteration support for Design Thinking coaching |
129129
| dt-quality-constraints | Quality constraints, fidelity rules, and output standards for Design Thinking coaching across all nine methods |
130130
| 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 |
131+
| dt-rpi-research-context | DT-aware task-researcher context — frames research around DT methods, stakeholder needs, and empathy-driven inquiry |
131132
| community-interaction | Community interaction voice, tone, and response templates for GitHub-facing agents and prompts |
132133
| github-backlog-discovery | Discovery protocol for GitHub backlog management - artifact-driven, user-centric, and search-based issue discovery |
133134
| github-backlog-planning | Reference specification for GitHub backlog management tooling - planning files, search protocols, similarity assessment, and state persistence |

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
../../../.github/instructions/design-thinking/dt-rpi-research-context.instructions.md

0 commit comments

Comments
 (0)