Dt Rpi Integration Agent Skill
Design Thinking handoff knowledge for research-ready rpi-research inputs and DT-aware rpi-plan, rpi-implement, and rpi-review context
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/microsoft/hve-core --skill dt-rpi-integrationWhat comes with it
39 138 bytes besides the instructionWhat it tells the agent to use
found in the instruction textThe instruction itself
3 sections, as written by the authorDesign 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.mdprovides DT-awarerpi-researchcontext.rpi-planning-context.mdprovides DT-awarerpi-plancontext.rpi-implement-context.mdprovides DT-awarerpi-implementcontext.rpi-review-context.mdprovides DT-awarerpi-reviewcontext.subagent-handoff.mdprovides the subagent dispatch workflow for handoff readiness, compilation, and validation.image-prompt-generation.mdprovides Method 5 lo-fi image prompt generation guidance.
Other skills for the same job
different authors, same section of the catalogue
Generate clinical trial protocols for medical devices or drugs. This skill should be used when users say "Create a clinical trial protocol", "Generate protocol for [device/drug]", "Help me design a clinical study", "Research similar trials for [intervention]", or when developing FDA submission documentation for investigational products.
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports continuous agent operation via Claude Code /loop and OpenClaw heartbeat, and produces research presentations and papers. Use when starting a research project, running autonomous experiments, or managing a multi-hypothesis research effort.
Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).
Generate and prioritize US equity long-side edge research tickets from EOD observations, then export pipeline-ready candidate specs for trade-strategy-pipeline Phase I. Use when users ask to turn hypotheses/anomalies into reproducible research tickets, convert validated ideas into `strategy.yaml` + `metadata.json`, or preflight-check interface compatibility (`edge-finder-candidate/v1`) before running pipeline backtests.
Use this skill when building or modifying Minecraft server plugins for Paper, Spigot, or Bukkit, including plugin.yml setup, commands, listeners, schedulers, player state, team or arena systems, persistent progression, economy or profile data, configuration files, Adventure text, and version-safe API usage. Trigger for requests like "build a Minecraft plugin", "add a Paper command", "fix a Bukkit listener", "create plugin.yml", "implement a minigame mechanic", "add a perk or quest system", or "debug server plugin behavior".
Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin
Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.
This skill should be used when designing autonomous agent harnesses: research loops, evaluation scaffolds, locked and editable surfaces, durable logs, novelty gates, pruning, rollback, PR preparation, and human approval boundaries.
How to use it
Take microsoft/dt-rpi-integration from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.