In this article
dt-rpi-integration
| Field | Value |
|---|---|
| Kind | skill |
| Source | .github/skills/design-thinking/dt-rpi-integration |
| Invocation | Loaded on demand by referencing agents |
| Interactive | No |
What it does
Design Thinking handoff knowledge for research-ready rpi-research inputs and DT-aware rpi-plan, rpi-implement, and rpi-review context
When to use it
DT Coach loads this pack when a team chooses to carry Design Thinking evidence
into engineering research. It supports exits after problem synthesis, tested
concepts, or implementation-space work. Every exit targets rpi-research; richer
evidence can narrow investigation but does not bypass Research, Plan, Implement,
or Review. RPI Agent can coordinate that lifecycle without replacing the handoff target.
Example usage
After a fictional Method 6 exercise, ask DT Coach to prepare a lateral RPI handoff
using dt-rpi-integration. Supply tested concepts, prototype observations,
constraint discoveries, and the narrowed directions. Keep an untested integration
assumption visible rather than marking it validated.
Expect a handoff summary with artifact paths, the exit point, rpi-research as
the target, and confidence markers of validated, assumed, unknown, or conflicting.
The coach records the chosen transition and frames a research-ready topic.
Success is enough traceable context for Research to verify gaps while preserving
stakeholder and fidelity constraints downstream. It is not implementation approval,
and conflicting evidence is not resolved by packaging it into a handoff.