Skip to content

feat(instructions): Create energy industry context template #588

@WilliamBerryiii

Description

@WilliamBerryiii

Overview

Create the energy industry context template, the second of three P0 industry templates. This provides energy-sector-specific vocabulary, constraints, empathy tools, and reference scenarios for DT coaching. Unlike the manufacturing template (which draws from 130+ DT4HVE references), this template is primarily original content informed by the energy sector's unique characteristics: critical infrastructure, long asset lifecycles, regulatory intensity, and the energy transition context.

Target File

.github/instructions/dt-industry-energy.instructions.md

Frontmatter

---
description: 'Energy industry context for DT coaching — vocabulary, constraints, empathy tools, and reference scenarios'
applyTo: ''
---

Required Content

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
  • Decision cadence: Real-time operations (seconds-minutes), maintenance scheduling (weekly-monthly), asset investment (5-30 year horizons), regulatory compliance (annual/multi-year)
  • Regulatory environment: NERC CIP, FERC, state utility commissions, EPA, DOE, emerging climate disclosure requirements

Vocabulary Mapping

DT Concept Energy Language
Stakeholder map RACI / Interconnection stakeholder register
Pain point Reliability concern / Outage root cause
User journey Asset lifecycle / Outage management workflow
Prototype Pilot project / Demonstration site
Iteration Continuous reliability improvement
Empathy Ride-along / Control room observation

Constraints and Considerations

  • Critical infrastructure: Design challenges may involve systems where failure has public safety implications; DT activities must never compromise operational reliability
  • Regulatory weight: Many processes exist because of regulation, not preference; understanding the regulatory driver is essential before redesigning
  • Long asset lifecycles: Solutions must account for 30-50 year asset lifecycles; what's innovative today must work decades from now
  • Jurisdiction complexity: Energy problems often span multiple regulatory jurisdictions with different rules
  • Workforce transition: Energy transition creates anxiety about job security; empathy work must be sensitive to this context
  • Security classification: Some operational data is classified under critical infrastructure protection rules

Empathy Tools

  • Control room observation: Watch operators manage grid operations, decision speed, information density, alarm fatigue
  • Field ride-along: Accompany field technicians to understand physical environment, safety rituals, and tool limitations
  • Regulatory timeline mapping: Map the regulatory calendar to understand when stakeholders are available vs. consumed by compliance deadlines
  • Intergenerational knowledge capture: Structured approach to understanding what experienced workers know that isn't documented

Reference Scenario

  • Context: Grid operations center struggling with renewable energy integration, intermittent generation creating new operational challenges
  • Stakeholders: Control room operators, renewable generation forecasters, market traders, transmission planners, field crews
  • Discovery: Traditional grid management assumptions break down with variable generation; operators are creating informal workarounds that aren't documented or shared
  • DT Journey: Methods 1-3 surface the human-system interaction challenges; Methods 4-6 generate solutions for operator decision support; Methods 7-9 pilot in controlled grid scenarios

Token Budget

Target: ~1,500-2,000 tokens (on-demand tier)

Source Material

Attach these files as context for the task-researcher phase:

  • Cumulative research: Design Thinking cumulative research, Part 7 (cross-industry strategy) for Industry Context Layer architecture and energy sector DT application patterns
  • Note: No existing DT4HVE energy-sector content; this template requires original content development informed by the energy sector's unique characteristics. Use the manufacturing template (feat(instructions): Create manufacturing industry context template #587) as structural reference.

RPI Pipeline Workflow

  1. task-researcher: Research energy sector DT applications, grid operations, asset management, regulatory compliance, workforce transition. Use DT4HVE energy references and supplement with domain knowledge.
  2. task-planner: Plan the template, industry profile, vocabulary mapping, constraints, empathy tools, reference scenario.
  3. task-implementor: Author following prompt-builder standards. Energy content is primarily original; maintain the same quality and structure as the manufacturing template.
  4. task-reviewer: Validate energy domain accuracy, critical infrastructure sensitivity, vocabulary mapping, prompt-builder compliance.

Starter Prompts

Research: /task-research — "Research energy sector DT applications — grid operations, asset management, regulatory compliance, workforce transition. No existing DT4HVE energy content; research domain knowledge and use manufacturing template as structural reference. Attach cumulative research Part 7 as context."

Plan: /task-plan — "Plan dt-industry-energy.instructions.md — industry profile, vocabulary mapping, constraints (critical infrastructure, regulatory weight, long asset lifecycles), empathy tools, reference scenario."

Implement: /task-implement — "Author dt-industry-energy.instructions.md following prompt-builder standards with empty applyTo, 1500-2000 token budget. Original content maintaining manufacturing template quality."

Review: /task-review — "Validate dt-industry-energy.instructions.md against prompt-builder standards, energy domain accuracy, and critical infrastructure sensitivity."

Prompt-Builder Compliance Checklist

Per .github/instructions/prompt-builder.instructions.md:

  • description: frontmatter present and descriptive
  • applyTo: '' (empty, on-demand loading)
  • Writing style uses guidance over commands (no "You must/will/shall")
  • Token count within budget tier
  • No ALL CAPS emphasis
  • Vocabulary mapping is bidirectional (DT→energy and energy→DT)

Success Criteria

  • Template created at .github/instructions/dt-industry-energy.instructions.md
  • Frontmatter has empty applyTo: (on-demand loading)
  • Industry profile covers key stakeholders, decision cadence, regulatory environment
  • Vocabulary mapping bridges DT and energy terminology
  • Constraints address critical infrastructure, regulatory weight, long asset lifecycles, security classification
  • Empathy tools are practical and energy-specific (control room observation, field ride-along)
  • Reference scenario demonstrates full DT journey in energy context
  • Token count within ~1,500-2,000 target
  • Passes task-reviewer validation against prompt-builder standards
  • Artifact registered in collections/design-thinking.collection.yml with path and kind fields
  • Artifact registered in collections/hve-core-all.collection.yml with path and kind fields
  • npm run plugin:generate run after updating collection manifests

Metadata

Metadata

Assignees

Labels

featureNew feature triggering minor version bumpinstructionsCopilot instruction files (.instructions.md)

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions