Dt Rpi Integration — Agent Skill by Microsoft

From the author

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

— the description by Microsoft

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/download

Unzip 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.md provides the per-space exit procedures, handoff summaries, transition entries, and RPI entry documents.
- 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.

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

references/rpi-implement-context.md

title: 'DT Implementation Context' description: Adjustments augmenting rpi-implement when executing plans that originated from a Design Thinking process.

When rpi-implement executes a plan that originated from a Design Thinking process, these adjustments augment the standard implementation workflow. The implementation phase does not receive direct DT handoffs; DT context arrives through rpi-research and rpi-plan. Fidelity constraints, stakeholder validation, and iteration support shape implementation decisions.

Implementation Adjustments

Standard Implementation	DT-Informed Implementation
Production-quality code	Space-appropriate fidelity (rough/scrappy/functional)
Complete feature delivery	Constraint-validated scope matching DT prototype specifications
Technical correctness focus	Stakeholder experience validation alongside technical correctness
Forward-only execution	Iteration-aware execution with return paths to earlier DT methods
Full polish and optimization	Anti-polish: functional core without premature optimization or visual refinement

DT-Specific Implementation Patterns

Enforce fidelity constraints from the originating DT space. Problem Space outputs are research-grade, Solution Space outputs are scrappy and concept-grade, and Implementation Space outputs are functionally rigorous without visual polish.
Verify implementation against each stakeholder group from the handoff's stakeholder map (an artifact of type stakeholder-map in the handoff artifacts array). When the handoff contains no stakeholder map artifact, flag this gap before proceeding.
Reference DT artifact paths (.copilot-tracking/dt/{project-slug}/) in RPI tracking artifacts, including the changes record, so decisions trace back to research and synthesis outputs. Keep tracking paths out of production code and code comments.
Treat handoff items marked assumed with explicit verification steps during implementation. Items marked unknown or conflicting require resolution before the affected implementation proceeds.
Support return paths to earlier DT methods as conditional outcomes within phase completion criteria rather than treating all implementation as forward-only.
For Solution Space implementations, enforce anti-polish: scope deliverables to scrappy fidelity and flag production-quality requests as out-of-scope for the current space.

Fidelity Constraints by DT Space

Originating Space	Implementation Fidelity
Problem Space (Methods 1-3)	Research-grade: outputs serve understanding, not production deployment
Solution Space (Methods 4-6)	Concept-grade: scrappy prototypes, paper-level fidelity, no production optimization
Implementation Space (Methods 7-9)	Functionally rigorous: working systems with real data, not visual polish

Return Path Triggers

Recommend returning to DT coaching rather than continuing implementation when any of these conditions emerge:

Implementation reveals that core assumptions validated during DT coaching do not hold under real-world constraints.
Stakeholder groups absent from the original stakeholder map surface during implementation.
Fidelity requirements for the deliverable exceed the originating space tier, indicating the team may have advanced too quickly through DT methods.
The prototype or concept validated during DT coaching fails under implementation constraints, requiring a return to Solution Space methods for redesign.

These adjustments complement co-loaded instruction files (dt-rpi-handoff-contract, dt-quality-constraints, dt-method-sequencing, dt-rpi-planning-context, dt-rpi-review-context): reference their content during implementation rather than duplicating it.

All DT coaching artifacts are scoped to .copilot-tracking/dt/{project-slug}/. Never write DT artifacts directly under .copilot-tracking/dt/ without a project-slug directory.

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.

Handoff
Matt Pocock· Community
Generates a concise handoff document to facilitate seamless transitions between AI agents.
Agent toolingClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub 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 more
MITGitHub 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 more
MITGitHub 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 more
MITGitHub 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 more
MITLow 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 more
MITGitHub 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