Dt Rpi Integration
MicrosoftOfficialPublished by Microsoft
- Skill
- Guidelines
- Agent tooling
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill acts as the bridge between Design Thinking coaching and the RPI (Research, Plan, Implement, Review) workflow. It defines the formal handoff contracts, artifact schemas, and contextual framing required to ensure that insights gathered during Design Thinking are effectively utilized by downstream RPI phases. It ensures that regardless of the Design Thinking exit point, all projects enter the RPI pipeline through the research phase with standardized, validated documentation.
What it does
- Defines the formal handoff contract for transitioning from Design Thinking to RPI phases.
- Provides standardized schemas for documenting handoff artifacts and project constraints.
- Offers guidance on framing research, planning, implementation, and review contexts based on DT artifacts.
- Includes procedures for subagent dispatch to validate handoff readiness.
- Provides specific instructions for generating lo-fi image prompts for concept visualization.
When to use it
- When a team graduates from a Design Thinking space boundary and needs to begin the RPI workflow.
- When you need to prepare research-ready inputs from completed Design Thinking methods.
- When you need to ensure that RPI planning and implementation phases are informed by validated DT context.
- When you need to generate neutral, lo-fi concept sketches for stakeholder evaluation.
Advantages
- Ensures continuity of project context across different development phases.
- Standardizes the quality and format of handoff documentation.
- Reduces investigation scope by providing validated artifacts from earlier stages.
- Maintains neutrality in visual concept generation through strict prompt enforcement.
Usage examples
- “How do I structure the handoff summary when moving from the Problem space to RPI research?”
- The agent provides the required YAML schema for the handoff-summary.md file, including fields for exit points, artifacts, and constraint tracking.
- “Generate a lo-fi image prompt for a concept where a technician uses a tablet to check inventory.”
- The agent generates a prompt following the required stick-figure template, ensuring no personal traits are included and the style is set to black-and-white line art.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/dt-rpi-integration/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip dt-rpi-integration.zip -d .agents/skills
Documentation by Microsoft
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 |
| Space-exit handoffs | Step-by-step Problem, Solution, and Implementation Space exit procedures that compile the handoff summary and the RPI entry document |
| 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.space-exit-handoffs.mdprovides the per-space exit procedures, handoff summaries, transition entries, and RPI entry documents.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.
Files
- ATTRIBUTION.mdAdded by AutoGineer887 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md3.7 KiB
- references/image-prompt-generation.md9.0 KiB
- references/rpi-handoff-contract.md7.2 KiB
- references/rpi-implement-context.md4.3 KiB
- references/rpi-planning-context.md5.8 KiB
- references/rpi-research-context.md4.2 KiB
- references/rpi-review-context.md6.1 KiB
- references/space-exit-handoffs.md17.3 KiB
- references/subagent-handoff.md3.3 KiB
SKILL.md
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 |
| Space-exit handoffs | Step-by-step Problem, Solution, and Implementation Space exit procedures that compile the handoff summary and the RPI entry document |
| 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.space-exit-handoffs.mdprovides the per-space exit procedures, handoff summaries, transition entries, and RPI entry documents.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.
Requirements and compatibility
Written for: GitHub Copilot, Claude Code
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Microsoft
- Publisher
- Microsoft (Official)
- Source
- microsoft/hve-core · .github/skills/design-thinking/dt-rpi-integration · commit f425e94
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Microsoft.
Related skills
Handoff
Matt Pocock· Community
Generates a concise handoff document to facilitate seamless transitions between AI agents.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Chief Of Staff
Matt Pocock· Community
A strategic orchestration agent that manages long-term goals by coordinating subagents and maintaining a persistent knowledge wiki.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Ask Matt
Matt Pocock· Community
A central routing skill that helps you identify the correct agent skill or workflow for your current situation.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Claude Handoff
Matt Pocock· Community
Seamlessly transfer your current conversation context to a new background agent.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository317.5k
Executing Plans
Jesse Vincent (obra)· Community
Execute implementation plans inline without subagents, maintaining rigorous progress tracking and verification.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskHas scriptsGitHub stars of the source repository314k
Using Superpowers
Jesse Vincent (obra)· Community
A mandatory protocol for AI agents to identify and invoke relevant skills before performing any task or responding to user input.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository314k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download dt-rpi-integration.zip