AutoGineer
Generated banner for Dt Rpi Integration
Generated logo for Dt Rpi Integration

Dt Rpi Integration

MicrosoftOfficialPublished by Microsoft

  • Skill
  • Guidelines
  • Agent tooling
  • MIT
  • No issues found
Download ZIP

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

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/dt-rpi-integration/download

  2. 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

ReferenceWhen to load
Handoff contractExit points, artifact schemas, RPI input contracts, and quality markers for lateral DT-to-RPI handoff
Space-exit handoffsStep-by-step Problem, Solution, and Implementation Space exit procedures that compile the handoff summary and the RPI entry document
Research contextDT-aware rpi-research framing for handoffs from the DT coach
Planning contextDT-aware rpi-plan context for plans originating from DT artifacts
Implement contextDT-aware rpi-implement context applying fidelity and stakeholder constraints
Review contextDT-aware rpi-review criteria for evaluating Design Thinking artifacts
Subagent handoffReadiness assessment, artifact compilation, and validation via subagent dispatch
Image prompt generationMethod 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

references/subagent-handoff.md

title: 'DT Subagent Handoff Workflow' description: Defines how the DT coach dispatches subagents during handoff transitions at Design Thinking space boundaries.

Defines how the DT coach dispatches subagents during handoff transitions at space boundaries. Mid-session research dispatch (quick queries during active coaching) is governed by the coach agent definition. This instruction governs the multi-step handoff workflow.

When a handoff uses a named agent, refer to it by its human-readable name in prose and reserve filename-style identifiers for file paths or glob references.

Readiness Assessment

When the coach detects graduation awareness at a space boundary, dispatch an assessment subagent with:

  • Current DT space (problem, solution, or implementation)

  • Expected artifacts per the exit-point schema from the handoff contract

  • Project directory path for artifact scanning

The subagent scans artifacts against the exit-point schema:

  1. Verify file existence for each expected artifact.

  2. Assess content completeness: non-empty files with key sections populated.

  3. Inventory quality markers: count validated, assumed, unknown, and conflicting items.

The subagent returns:

  • Readiness status: Ready, Partially Ready, or Not Ready

  • Missing artifacts list

  • Quality summary (for example, "3 validated insights, 2 unknown assumptions, 1 conflicting data point")

  • Recommended actions when not fully ready

Artifact Compilation

When the user confirms handoff and readiness is acceptable, dispatch a compilation subagent with:

  • Exit-point schema template from the handoff contract

  • Project artifact directory paths

  • Quality marker definitions

The subagent reads and compiles method artifacts into the exit schema:

  1. Extract key content from each method's output files.

  2. Apply quality markers based on artifact content and coaching history.

  3. Generate the structured exit-point artifact with confidence annotations.

The subagent returns the compiled artifact. The coach reviews and adjusts it, then follows the space-exit handoff procedure in space-exit-handoffs.md for the space the team is leaving.

Handoff Validation

After the space-exit handoff procedure generates the RPI entry artifact, dispatch a validation subagent with:

  • Generated RPI entry artifact

  • RPI input contract for the target agent

  • Content sanitization rules

The subagent validates:

  1. All required RPI input fields are populated.

  2. No .copilot-tracking/ paths appear in the artifact.

  3. No planning reference IDs leak into the artifact.

  4. Quality markers are present and consistent with source data.

The subagent returns a validation result: Pass or Fail with specific issues listed.

Session Continuity

During all subagent dispatch:

  • Coaching state remains read-only for subagents. Only the coach modifies state.

  • Coach identity and hint calibration persist across dispatch boundaries.

  • If subagent dispatch fails, the coach presents assessment or compilation manually with reduced detail.

  • Inform the user that background work is in progress ("Let me check our readiness for handoff...").

  • 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.

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.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download dt-rpi-integration.zip