feat(design-thinking): add manufacturing industry context template (#682)

# Pull Request

## Description

Add on-demand instruction file for manufacturing industry context that
provides vocabulary mapping, operational constraints, empathy tools, and
a reference scenario for contextualizing Design Thinking coaching in
manufacturing environments.

The manufacturing template is the first industry context module,
establishing the pattern for future industry templates (healthcare,
etc.). It follows the on-demand tier loading pattern (`applyTo: ''`) so
the coach loads it only when manufacturing context is relevant.

## Related Issue(s)

Closes #587

## Type of Change

Select all that apply:

**AI Artifacts:**

- [x] Copilot instructions (`.github/instructions/*.instructions.md`)

## Sample Prompts (for AI Artifact Contributions)

**User Request:**

> "We're working with a manufacturing client that has quality variance
across shifts. Help us plan our scope conversations."

**Execution Flow:**

1. DT Coach detects manufacturing industry context from the user's
description
2. Coach loads `dt-industry-manufacturing.instructions.md` on demand
3. Vocabulary mapping translates DT terminology to manufacturing
equivalents (e.g., "stakeholder interview" → "operator ride-along")
4. Constraints section surfaces safety culture, shift patterns, and
union dynamics
5. Empathy tools guide gemba walks, shift-handoff observations, and
operator shadows
6. Reference scenario provides a concrete quality-variance-across-shifts
journey through all 3 DT spaces

**Output Artifacts:**

- Coaching interactions use manufacturing vocabulary naturally
- Constraint-aware recommendations (e.g., scheduling around shift
changes, mandatory PPE for observations)
- Industry-appropriate empathy tool suggestions

**Success Indicators:**

- Coach uses bidirectional vocabulary mapping when discussing
manufacturing engagements
- Constraint sections prevent coaching recommendations that conflict
with manufacturing realities
- Reference scenario provides concrete examples the team can relate to

## Testing

- `npm run plugin:generate` — 11 plugins generated, 0 errors
- `npm run lint:all` — 0 markdown errors, 0 frontmatter errors, 0
collection metadata errors (only `actionlint` not installed locally)

## Checklist

### Required Checks

- [x] Documentation is updated (if applicable)
- [x] Files follow existing naming conventions
- [x] Changes are backwards compatible (if applicable)
- [ ] Tests added for new functionality (if applicable)

### Required Automated Checks

- [x] Markdown linting: `npm run lint:md`
- [ ] Spell checking: `npm run spell-check`
- [x] Frontmatter validation: `npm run lint:frontmatter`
- [x] Skill structure validation: `npm run validate:skills`
- [ ] Link validation: `npm run lint:md-links`
- [x] PowerShell analysis: `npm run lint:ps`

## Security Considerations

- [x] This PR does not contain any sensitive or NDA information
- [x] Any new dependencies have been reviewed for security issues
- [x] Security-related scripts follow the principle of least privilege

## Additional Notes

- First industry context template — establishes the pattern for future
industry modules (#589 healthcare)
- On-demand tier (`applyTo: ''`) — loaded only when the coach detects
manufacturing context
- Registered in `design-thinking` and `hve-core-all` collections
- Plugin outputs regenerated

---------

Co-authored-by: Bill Berry <wbery@microsoft.com>

Author: chaosdinosaur

.cspell.json

@@ -51,6 +51,7 @@
     "docker",
     "rust",
     "data-science",
+    "design-thinking",
     "aws",
     "terraform",
     "azure-services",
@@ -65,9 +66,9 @@
     "Browsable",
     "Chronograf",
     "edgeai",
+    "gemba",
     "GHCP",
     "GHSA",
-
     "Kapacitor",
     "kata",
     "katas",

.github/instructions/design-thinking/dt-industry-manufacturing.instructions.md

@@ -0,0 +1,89 @@
+---
+description: 'Manufacturing industry context for DT coaching — vocabulary, constraints, empathy tools, and reference scenarios'
+applyTo: ''
+---
+
+# Manufacturing Industry Context
+
+Load this file when the team identifies manufacturing as their industry context. It provides manufacturing-specific vocabulary, constraints, empathy tools, and a reference scenario that the coach weaves into method-specific guidance.
+
+## Industry Profile
+
+* **Sector**: Discrete and process manufacturing
+* **Key stakeholders**: Operators, shift supervisors, maintenance engineers, quality engineers, safety/compliance officers, plant managers, union representatives, IT support
+* **Decision cadence**: Shift-level (8-12 hours), daily stand-ups, weekly production reviews, quarterly/annual capital investment
+* **Regulatory environment**: OSHA, EPA, ISO 9001/14001, industry-specific standards (FDA for pharma, IATF 16949 for automotive)
+* **Missing voices to seek out**: Night/weekend shift workers, seasonal or temporary staff, new hires, contract workers
+
+## Vocabulary Mapping
+
+Bridge DT language and manufacturing language bidirectionally. Use manufacturing terms when coaching manufacturing teams.
+
+| DT Concept                | Manufacturing Term                            |
+|---------------------------|-----------------------------------------------|
+| Stakeholder map           | RACI chart, responsibility matrix             |
+| Pain point                | Downtime cause, production bottleneck         |
+| User journey              | Production workflow, value stream             |
+| Observation / field study | Gemba walk, operator ride-along               |
+| Prototype                 | Pilot run, trial batch, proof of concept      |
+| Iteration                 | Continuous improvement, Kaizen cycle          |
+| Empathy                   | Gemba (go and see), operator perspective      |
+| Success metric            | OEE, MTTR, first-pass yield, downtime minutes |
+| Workflow mapping          | SOP review, value stream mapping              |
+| Risk assumption           | FMEA (Failure Mode and Effects Analysis)      |
+| Constraint-driven design  | Poka-yoke (mistake-proofing)                  |
+| Alert system concept      | Andon (signal for help)                       |
+| Integration timing        | Takt time                                     |
+
+## Constraints and Considerations
+
+### Safety
+
+Safety is non-negotiable scope, not a preference. Safety and compliance officers hold effective veto power over solutions affecting worker safety or regulatory status. Changes involving safety, environmental controls, or quality certification require regulatory review before deployment.
+
+### Shifts
+
+Day shifts have management oversight and support resources. Night and weekend shifts operate with reduced staffing and develop workarounds invisible to day management. A solution scoped entirely from day-shift observations may fail during off-hours. Include representatives from multiple shifts in stakeholder mapping and testing.
+
+### Unions
+
+Union representatives are stakeholders with effective veto power alongside regulators and safety officers. Labor agreements can constrain process changes and technology deployment. Engage union representatives early in the coaching process.
+
+### Physical Environment
+
+* **Noise**: 85-90 dB on production floors prevents normal voice interaction and requires hearing protection
+* **Contamination**: Greasy or chemical-coated hands prevent touchscreen use; solutions need glove-friendly or hands-free interaction
+* **Lighting**: Factory lighting affects screen readability and QR code scanning
+* **Space**: Production line constraints limit device placement and prototype testing areas
+
+### Data Sensitivity
+
+Machine sensor data, production metrics, and maintenance logs contain operational IP. Telemetry collection requires alignment with plant management and IT. Performance reports used for synthesis may have access restrictions.
+
+## Empathy Tools
+
+### Gemba Walk
+
+Structured observation on the factory floor. Walk the production line during active operations. Observe what workers actually do versus documented SOPs. Note workarounds, informal communication channels, and environmental constraints. Conversations are most productive during natural work pauses, not interruptions. Respect PPE requirements and designated observation areas.
+
+### Shift Handoff Observation
+
+Watch shift transitions to identify information loss, miscommunication, and undocumented workarounds. Shift handoff is a frequent source of scope-relevant problems. Compare what day shift documents versus what night shift actually receives.
+
+### Operator Shadow
+
+Follow an operator through a complete shift or task cycle. Observe actual workflow, not the documented version. Use progressive questioning: start with "walk me through your typical day" before drilling into specific tasks. Watch for moments where the operator hesitates, improvises, or works around a limitation.
+
+### Safety Incident Narrative
+
+Use anonymized incident reports and near-miss data as empathy artifacts. These reveal the operator's experience under pressure, failure cascade patterns, and gaps between documented procedures and real conditions. Emergency procedures often surface the highest-value use cases.
+
+## Reference Scenario
+
+**Context**: A manufacturing plant experiences quality variance across shifts. Day shifts consistently outperform night shifts on first-pass yield.
+
+**Discovery (Methods 1-3)**: Scope conversations reveal the initial request is "build a quality dashboard." Gemba walks on both shifts and shift-handoff observations uncover the real problem: information asymmetry. Night-shift operators have the same equipment and SOPs but lack the informal knowledge transfer, rapid-response support, and management oversight that day shifts enjoy. Workers spend 10-15 minutes finding manual sections while actual repairs take 5-10 minutes.
+
+**Solution (Methods 4-6)**: Brainstorming generates four solution themes: hands-free interaction, visual guidance, collaborative knowledge sharing, and proactive assistance. Lo-fi prototypes reveal touchscreen contamination, QR code lighting issues, and production-timing conflicts — constraints invisible from a desk.
+
+**Implementation (Methods 7-9)**: Hi-fi prototypes validate industrial-grade microphones for 85-90 dB environments and glove-friendly interfaces. User testing across four operator types shows 40% higher adoption with glove-friendly design. Shift-change usage spikes lead to dedicated transition features. Emergency stop procedures are used 300% above forecast, revealing safety as the highest-value use case.

collections/design-thinking.collection.md

@@ -17,3 +17,4 @@ This collection includes agents, prompts, and instructions for:
 - **DT Method 07: High-Fidelity Prototypes** — Technical translation, functional prototypes, and specifications for Implementation Space entry with three-hat architecture and progressive fidelity modeling
 - **DT Method 07: Deep Expertise** — On-demand fidelity translation, architecture trade-off analysis, specification writing patterns, and manufacturing-specific prototyping guidance for complex Method 7 coaching scenarios
 - **DT Method 08: User Testing** — Evidence-based evaluation, test protocols, and non-linear iteration support for structured user testing of hi-fi prototypes with leap-enabling questioning and loop decision coaching
+- **DT Industry: Manufacturing** — On-demand industry context providing manufacturing vocabulary mapping, operational constraints (safety culture, shift patterns, union dynamics), empathy tools (gemba walk, shift-handoff observation, operator shadow), and a reference scenario for contextualizing Design Thinking coaching in manufacturing environments

collections/design-thinking.collection.yml

@@ -44,5 +44,7 @@ items:
     kind: instruction
   - path: .github/instructions/design-thinking/dt-method-03-synthesis.instructions.md
     kind: instruction
+  - path: .github/instructions/design-thinking/dt-industry-manufacturing.instructions.md
+    kind: instruction
 display:
   ordering: alpha

collections/hve-core-all.collection.yml

@@ -166,6 +166,8 @@ items:
   kind: instruction
 - path: .github/instructions/design-thinking/dt-coaching-state.instructions.md
   kind: instruction
+- path: .github/instructions/design-thinking/dt-industry-manufacturing.instructions.md
+  kind: instruction
 - path: .github/instructions/design-thinking/dt-method-01-deep.instructions.md
   kind: instruction
 - path: .github/instructions/design-thinking/dt-method-01-scope.instructions.md

plugins/design-thinking/README.md

@@ -39,6 +39,7 @@ copilot plugin install design-thinking@hve-core
 | dt-method-03-deep            | Deep expertise for Method 3: Input Synthesis — advanced affinity analysis, insight frameworks, and problem statement articulation                                                                                                          |
 | dt-method-02-research        | Method 2 Design Research coaching knowledge: interview techniques, research planning, environmental observation, and insight extraction patterns                                                                                           |
 | dt-method-03-synthesis       | Method 3 Input Synthesis coaching knowledge: pattern recognition, theme development, synthesis validation, and Problem-to-Solution Space transition readiness                                                                              |
+| dt-industry-manufacturing    | Manufacturing industry context for DT coaching — vocabulary, constraints, empathy tools, and reference scenarios                                                                                                                           |
 
 ---
 

plugins/design-thinking/instructions/dt-industry-manufacturing.md

@@ -0,0 +1 @@
+../../../.github/instructions/design-thinking/dt-industry-manufacturing.instructions.md

plugins/hve-core-all/README.md

@@ -100,6 +100,7 @@ copilot plugin install hve-core-all@hve-core
 | uv-projects                  | Create and manage Python virtual environments using uv commands                                                                                                                                                                                             |
 | dt-coaching-identity         | Required instructions when working with or doing any Design Thinking (DT); Contains instructions for the Design Thinking coach identity, philosophy, and user interaction and communication requirements for consistent coaching behavior.                  |
 | dt-coaching-state            | Coaching state schema for Design Thinking session persistence, method progress tracking, and session recovery                                                                                                                                               |
+| dt-industry-manufacturing    | Manufacturing industry context for DT coaching — vocabulary, constraints, empathy tools, and reference scenarios                                                                                                                                            |
 | dt-method-01-deep            | Deep expertise for Method 1: Scope Conversations, covering advanced stakeholder analysis, power dynamics, and scope negotiation                                                                                                                             |
 | dt-method-01-scope           | Method 1 Scope Conversations coaching knowledge for Design Thinking: frozen vs fluid assessment, stakeholder discovery, constraint patterns, and conversation navigation                                                                                    |
 | dt-method-02-research        | Method 2 Design Research coaching knowledge: interview techniques, research planning, environmental observation, and insight extraction patterns                                                                                                            |

plugins/hve-core-all/instructions/dt-industry-manufacturing.md

@@ -0,0 +1 @@
+../../../.github/instructions/design-thinking/dt-industry-manufacturing.instructions.md