mcpbeat

Dt Rpi Integration

microsoft/dt-rpi-integration

Design Thinking handoff knowledge for research-ready rpi-research inputs and DT-aware rpi-plan, rpi-implement, and rpi-review context

11k tokens
context cost
the whole folder, loaded on every use
8
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1313
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/microsoft/hve-core --skill dt-rpi-integration

What comes with it

39 138 bytes besides the instruction
references/image-prompt-generation.md
references/rpi-handoff-contract.md
references/rpi-implement-context.md
references/rpi-planning-context.md
references/rpi-research-context.md
references/rpi-review-context.md
references/subagent-handoff.md

What it tells the agent to use

found in the instruction text
Task spawns other agents

The instruction itself

3 sections, as written by the author

Design Thinking → RPI Integration — Skill Entry

This skill is the entry point for Design Thinking to RPI integration knowledge.

The DT coach loads these references when Design Thinking coaching graduates into the RPI workflow. Every DT exit produces research-ready input for rpi-research. The retained downstream phases, rpi-plan, rpi-implement, and rpi-review, consume the resulting context. RPI Agent is the lifecycle wrapper when end-to-end coordination is needed; it does not replace rpi-research as the handoff target.

Integration references

| Reference | When to load |

|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|

| Handoff contract | Exit points, artifact schemas, RPI input contracts, and quality markers for lateral DT-to-RPI handoff |

| Research context | DT-aware rpi-research framing for handoffs from the DT coach |

| Planning context | DT-aware rpi-plan context for plans originating from DT artifacts |

| Implement context | DT-aware rpi-implement context applying fidelity and stakeholder constraints |

| Review context | DT-aware rpi-review criteria for evaluating Design Thinking artifacts |

| Subagent handoff | Readiness assessment, artifact compilation, and validation via subagent dispatch |

| Image prompt generation | Method 5 concept visualization with lo-fi prompt enforcement |

Skill layout

  • SKILL.md — this file (skill entrypoint).
  • references/ — the DT-to-RPI integration reference documents.
  • rpi-handoff-contract.md — DT-to-RPI handoff contract: exit points, artifact schemas, RPI input contracts, and confidence markers.
  • rpi-research-context.md provides DT-aware rpi-research context.
  • rpi-planning-context.md provides DT-aware rpi-plan context.
  • rpi-implement-context.md provides DT-aware rpi-implement context.
  • rpi-review-context.md provides DT-aware rpi-review context.
  • subagent-handoff.md provides the subagent dispatch workflow for handoff readiness, compilation, and validation.
  • image-prompt-generation.md provides Method 5 lo-fi image prompt generation guidance.

How to use it

Copy the folder

Take microsoft/dt-rpi-integration from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.