Dt Methods
MicrosoftOfficialPublished by Microsoft
- Skill
- Guidelines
- Business and productivity
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The dt-methods skill provides a structured reference system for AI agents to coach teams through the Design Thinking process. It organizes guidance into three layers: core method references for day-to-day activities, deep references for advanced facilitation and recovery, and industry-specific context to tailor vocabulary and constraints. The skill covers nine major industries, including energy, healthcare, and financial services, ensuring that coaching is grounded in the specific operational realities and regulatory environments of the user's sector.
What it does
- Provides step-by-step guidance for nine core Design Thinking methods.
- Offers advanced facilitation techniques and recovery strategies for complex scenarios.
- Maps Design Thinking concepts to industry-specific terminology and constraints.
- Integrates telemetry expectations for session artifacts to ensure observable outcomes.
- Supplies industry-specific empathy tools and stakeholder considerations.
- Supports tailoring of coaching based on the active method and identified industry context.
When to use it
- When facilitating a Design Thinking session and requiring method-specific guidance.
- When a team needs advanced troubleshooting or recovery techniques during a workshop.
- When applying Design Thinking within a specific industry to ensure relevant vocabulary and constraints are respected.
- When defining telemetry or audit trails for Design Thinking session artifacts.
Advantages
- Ensures consistent coaching across the entire Design Thinking lifecycle.
- Reduces friction by using industry-appropriate language and concepts.
- Provides a clear path for scaling from basic methods to advanced facilitation.
- Integrates operational and regulatory awareness into the design process.
Usage examples
- “How should I facilitate a brainstorming session for a team in the energy sector?”
- The agent will load the brainstorming method reference and the energy industry context, providing guidance that uses energy-specific terms like 'reliability concern' and 'forced outage rate' while emphasizing safety and regulatory constraints.
- “We are stuck during the user research phase; what advanced techniques can we use?”
- The agent will access the deep reference for the Design Research method to provide advanced facilitation strategies and recovery techniques to help the team overcome their current roadblock.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/microsoft/dt-methods/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip dt-methods.zip -d .agents/skills
Documentation by Microsoft
Design Thinking Methods Skill
Entrypoint for Design Thinking method coaching knowledge. The dt-coach agent loads the method reference matching the active method in coaching state, the matching deep reference when advanced technique is needed, and the industry reference when an industry context applies.
How to use this skill
Read the method reference for the method currently active in coaching state to ground day-to-day coaching.
Read the matching deep reference when the conversation needs advanced facilitation, recovery techniques, or expert frameworks beyond the core method guidance.
Read the industry reference when the team has identified one of the nine covered industries as their context, and weave its vocabulary, constraints, and empathy tools into method-specific guidance.
Read dt-coach-telemetry.md when DT session artifacts need observable telemetry expectations grounded in
telemetry-foundations.
Method references
| Method | Name | Core reference | Deep reference |
|---|---|---|---|
| 1 | Scope Conversations | method-01-scope.md | method-01-deep.md |
| 2 | Design Research | method-02-research.md | method-02-deep.md |
| 3 | Input Synthesis | method-03-synthesis.md | method-03-deep.md |
| 4 | Brainstorming | method-04-brainstorming.md | method-04-deep.md |
| 5 | User Concepts | method-05-concepts.md | method-05-deep.md |
| 6 | Low-Fidelity Prototypes | method-06-lofi-prototypes.md | method-06-deep.md |
| 7 | High-Fidelity Prototypes | method-07-hifi-prototypes.md | method-07-deep.md |
| 8 | User Testing | method-08-testing.md | method-08-deep.md |
| 9 | Iteration at Scale | method-09-iteration.md | method-09-deep.md |
Industry context references
Load the matching reference when the team identifies its industry context.
| Reference | When to load |
|---|---|
| industry-energy.md | Energy-sector vocabulary, constraints, empathy tools, and reference scenario. |
| industry-financial-services.md | Financial services vocabulary, constraints, empathy tools, and reference scenario. |
| industry-healthcare.md | Healthcare vocabulary, constraints, empathy tools, and reference scenario. |
| industry-manufacturing.md | Manufacturing vocabulary, constraints, empathy tools, and reference scenario. |
| industry-nonprofit-social-impact.md | Nonprofit and social impact vocabulary, constraints, empathy tools, and reference scenario. |
| industry-pharmaceuticals-life-sciences.md | Pharmaceuticals and life sciences vocabulary, constraints, empathy tools, and reference scenario. |
| industry-professional-services.md | Professional services vocabulary, constraints, empathy tools, and reference scenario. |
| industry-public-sector.md | Public sector and government vocabulary, constraints, empathy tools, and reference scenario. |
| industry-retail-cpg.md | Retail and consumer goods vocabulary, constraints, empathy tools, and reference scenario. |
Skill layout
.
├── SKILL.md
└── references/
├── method-01-scope.md
├── method-01-deep.md
├── method-02-research.md
├── method-02-deep.md
├── method-03-synthesis.md
├── method-03-deep.md
├── method-04-brainstorming.md
├── method-04-deep.md
├── method-05-concepts.md
├── method-05-deep.md
├── method-06-lofi-prototypes.md
├── method-06-deep.md
├── method-07-hifi-prototypes.md
├── method-07-deep.md
├── method-08-testing.md
├── method-08-deep.md
├── method-09-iteration.md
├── method-09-deep.md
├── industry-energy.md
├── industry-financial-services.md
├── industry-healthcare.md
├── industry-manufacturing.md
├── industry-nonprofit-social-impact.md
├── industry-pharmaceuticals-life-sciences.md
├── industry-professional-services.md
├── industry-public-sector.md
├── industry-retail-cpg.md
└── dt-coach-telemetry.mdFiles
- ATTRIBUTION.mdAdded by AutoGineer871 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md6.5 KiB
- references/dt-coach-telemetry.md1.5 KiB
- references/industry-energy.md9.1 KiB
- references/industry-financial-services.md10.7 KiB
- references/industry-healthcare.md7.7 KiB
- references/industry-manufacturing.md6.7 KiB
- references/industry-nonprofit-social-impact.md15.6 KiB
- references/industry-pharmaceuticals-life-sciences.md20.1 KiB
- references/industry-professional-services.md14.0 KiB
- references/industry-public-sector.md12.1 KiB
- references/industry-retail-cpg.md16.5 KiB
- references/method-01-deep.md10.4 KiB
- references/method-01-scope.md10.2 KiB
- references/method-02-deep.md15.6 KiB
- references/method-02-research.md7.0 KiB
- references/method-03-deep.md13.9 KiB
- references/method-03-synthesis.md8.9 KiB
- references/method-04-brainstorming.md13.6 KiB
- references/method-04-deep.md16.5 KiB
- references/method-05-concepts.md17.1 KiB
- references/method-05-deep.md17.7 KiB
- references/method-06-deep.md16.3 KiB
- references/method-06-lofi-prototypes.md17.2 KiB
- references/method-07-deep.md10.9 KiB
- references/method-07-hifi-prototypes.md9.8 KiB
- references/method-08-deep.md15.0 KiB
- references/method-08-testing.md11.5 KiB
- references/method-09-deep.md17.2 KiB
- references/method-09-iteration.md11.9 KiB
references/industry-energy.md
title: Energy Industry Context description: Energy industry context, vocabulary, and constraints for tailoring Design Thinking methods to this sector.
Load this file when the team identifies energy as their industry context. It provides energy-sector vocabulary, constraints, empathy tools, and a reference scenario that the coach weaves into method-specific guidance.
Industry Profile
Sector: Energy (generation, transmission, distribution, renewables integration)
Key stakeholders: Control room operators, field technicians, grid engineers, reliability engineers, environmental compliance officers, asset managers, regulatory affairs, community relations, market traders, renewable generation forecasters
Decision cadence: Real-time operations (seconds to minutes), maintenance scheduling (weekly to monthly), asset investment (5-30 year horizons), regulatory compliance (annual and multi-year cycles)
Regulatory environment: NERC CIP (critical infrastructure protection), FERC, state utility commissions, EPA, DOE, emerging climate disclosure requirements
Missing voices to seek out: Night-shift control room operators, field crews in remote locations, substation technicians, community members near generation or transmission assets, contract workers during seasonal peaks
Vocabulary Mapping
Bridge DT language and energy language bidirectionally. Use energy terms when coaching energy teams.
| DT Concept | Energy Term |
|---|---|
| Stakeholder map | RACI, interconnection stakeholder register |
| Pain point | Reliability concern, outage root cause |
| User journey | Asset lifecycle, outage management workflow |
| Observation / field study | Control room observation, field ride-along |
| Prototype | Pilot project, demonstration site |
| Iteration | Continuous reliability improvement cycle |
| Empathy | Ride-along, control room observation |
| Success metric | SAIDI, SAIFI, CAIDI, forced outage rate, capacity factor |
| Workflow mapping | Switching order sequence, outage coordination process |
| Risk assumption | Contingency analysis, N-1 / N-2 reliability criteria |
| Constraint-driven design | Operating procedure, protection scheme |
| Alert system concept | SCADA alarm, energy management system alert |
| Integration timing | Interconnection queue position, in-service date |
Constraints and Considerations
Critical Infrastructure
Energy systems are critical infrastructure where failure has direct public safety implications. DT activities must never compromise operational reliability. Observation and research activities in control rooms and substations require coordination with operations management before scheduling. Solutions touching grid operations need reliability review before any pilot deployment.
Regulatory Weight
Many energy processes exist because of regulation, not preference. NERC CIP standards govern cybersecurity for bulk electric systems. FERC orders define market rules and transmission access. State commissions set rate structures and service standards. Understanding the regulatory driver behind a process is essential before redesigning it — what looks like inefficiency may be a compliance requirement.
Long Asset Lifecycles
Energy infrastructure operates on 30-50 year asset lifecycles. Transmission lines, substations, and generation facilities represent decades of capital investment. Solutions must account for this time horizon — what is innovative today must integrate with assets that will operate for decades. Design decisions carry long-term operational consequences that are difficult to reverse.
Jurisdiction Complexity
Energy problems often span multiple regulatory jurisdictions with different rules. A single transmission project may cross state lines, involve multiple utility territories, and require federal, state, and local approvals. Stakeholder mapping must account for this multi-jurisdictional landscape. Solutions that work in one jurisdiction may face different requirements in the next.
Workforce Transition
The energy transition from fossil fuels to renewables creates anxiety about job security and skill relevance. Empathy work must be sensitive to this context. Workers with decades of experience in conventional generation may feel threatened by changes. Frame design thinking as enhancing their expertise, not replacing it. Include transition-affected workers as stakeholders, not just subjects.
Security Classification
Some operational data falls under NERC CIP critical infrastructure protection rules. SCADA data, network topology, and protection settings may be classified. Empathy artifacts (photos, diagrams, notes) from control rooms and substations may require security review before sharing outside the utility. Prototypes handling grid operational data need cybersecurity review even in pilot form.
Empathy Tools
Control Room Observation
Observe operators managing grid operations during normal and high-stress periods. Track decision speed, information density, screen navigation patterns, and alarm fatigue. Control rooms operate 24/7 with shift rotations — observe multiple shifts to capture different operating conditions. Morning peak and evening ramp are high-cognitive-load periods where workarounds surface. Coordinate scheduling with the shift supervisor and respect operational priority at all times.
Field Ride-Along
Accompany field technicians to substations, transmission corridors, or generation sites. Observe the physical environment, safety rituals (tailboard meetings, lockout/tagout), tool limitations, and communication challenges in remote locations. Field work is weather-dependent and physically demanding — respect conditions that affect scheduling. Note the gap between what planning systems assume and what field crews actually encounter.
Regulatory Timeline Mapping
Map the regulatory calendar to understand when stakeholders are available versus consumed by compliance deadlines. NERC CIP audits, FERC filings, integrated resource plan submissions, and rate case proceedings consume significant staff attention on fixed schedules. Schedule DT activities during regulatory lulls, not during filing seasons when key stakeholders are unavailable.
Intergenerational Knowledge Capture
Structured approach to understanding what experienced workers know that is not documented. Senior operators and engineers carry decades of institutional knowledge about system behavior, failure patterns, and informal procedures. Pair experienced workers with newer staff during observation sessions. Capture knowledge about edge cases, seasonal patterns, and historical context that formal documentation misses.
Reference Scenario
Context: A grid operations center struggles with renewable energy integration as intermittent wind and solar generation creates operational challenges that traditional grid management assumptions do not address.
Discovery (Methods 1-3): Scope conversations reveal the initial request is "build a better renewable forecasting dashboard." Control room observations and field ride-alongs across shifts uncover the real problem: operators are creating informal workarounds to manage generation variability that existing tools do not support. Experienced operators mentally compensate for forecast errors using pattern knowledge they cannot articulate. Newer operators lack this tacit expertise and fall back on conservative dispatch decisions that increase costs.
Solution (Methods 4-6): Brainstorming generates solution themes: operator decision support for variable generation, forecast confidence visualization, automated pre-positioning of reserves, and shift handoff tools for renewable conditions. Lo-fi prototypes — paper mockups of enhanced dispatch screens and revised handoff checklists — reveal that operators need different information granularity depending on renewable penetration levels. Security constraints surface when prototype screen designs expose grid topology details restricted under NERC CIP.
Implementation (Methods 7-9): Hi-fi prototypes validate operator decision support tools integrated with the energy management system, tested through grid simulation before live deployment. User testing across shifts reveals that night-shift operators face different renewable challenges (wind peaks) than day-shift operators (solar ramps). Operator confidence in managing high-renewable periods improves measurably during pilot. Iteration focuses on alarm management — operators report alarm fatigue from renewable variability triggers that existing thresholds were not designed to handle.
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-methods · 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 or Microsoft.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download dt-methods.zip