feat(instructions): Create DT curriculum content

[WilliamBerryiii]

Overview

Create curriculum instruction files that the dt-learning-tutor loads when delivering DT methodology education. These files transform the DT4HVE guidance layer content into structured teaching modules — each method gets a curriculum instruction file with key concepts, technique explanations, comprehension questions, and practice exercises. The curriculum content is separate from the method-tier instructions used by dt-coach because teaching requires different framing: explanation over facilitation, assessment over artifact production.

Target Files

.github/instructions/dt-curriculum-*.instructions.md — one per DT method (9 files total):

• dt-curriculum-01-scoping.instructions.md
• dt-curriculum-02-research.instructions.md
• dt-curriculum-03-synthesis.instructions.md
• dt-curriculum-04-brainstorming.instructions.md
• dt-curriculum-05-concepts.instructions.md
• dt-curriculum-06-prototypes.instructions.md
• dt-curriculum-07-testing.instructions.md
• dt-curriculum-08-iteration.instructions.md
• dt-curriculum-09-handoff.instructions.md

Frontmatter Pattern

Each curriculum file uses an applyTo pattern that activates when the tutor is working with that module's content:

---
description: 'DT Curriculum Module N: [Method Name] — key concepts, techniques, comprehension checks, and practice exercises'
applyTo: '**/.copilot-tracking/dt/**/curriculum-{NN}*'
---

Required Content Per Module

Each curriculum instruction file contains these sections:

Module Overview

A 2-3 sentence explanation of what this method accomplishes, where it sits in the overall DT flow (Problem Space / Solution Space / Implementation Space), and why it matters. Written in teaching voice — explaining to a learner rather than facilitating a practitioner.

Key Concepts

Core vocabulary and principles for this method. Each concept includes:

• Term: The concept name
• Definition: Plain-language explanation
• Why it matters: Connection to the method's purpose
• Common misconception: What learners often get wrong

Example concepts per method: divergent vs convergent thinking (Brainstorming), desirability/feasibility/viability (Concepts), fidelity levels (Prototypes).

Techniques

Specific techniques used in this method, explained for learning rather than doing:

• What the technique is and when to use it
• How it works step by step
• What good output looks like
• Common pitfalls

Comprehension Checks

3-5 questions per module that verify understanding. Questions should be:

• Conceptual (not trivia): "Why does Method 3 synthesize before ideating?" not "What is Method 3 called?"
• Scenario-based when possible: "A team has 40 interview transcripts but no clear patterns. Which synthesis technique would you recommend and why?"
• Progressive: Earlier modules have simpler checks; later modules connect across methods

Practice Exercises

Lightweight exercises using the manufacturing reference scenario (#618). Each exercise:

• Applies one technique from the module
• Produces a small artifact the tutor can review
• Takes 5-10 minutes of learner effort
• Connects to the ongoing reference scenario for continuity

Learner Level Adaptations

Notes for tutor behavior at each level:

• Beginner: Focus on key concepts and basic technique walkthroughs
• Intermediate: Add technique comparisons and cross-method connections
• Advanced: Include edge cases, methodology critiques, and integration challenges

Token Budget

Target: ~1,000-1,500 tokens per curriculum file (loaded by tutor when delivering specific module)

How to Build This File

These are .instructions.md files — use the prompt-builder agent (not task-implementor) for the authoring phase.

Workflow: /task-research → /task-plan → /prompt-build → /task-review

Between each phase, use /clear to reset context, then attach the output artifact from the previous phase as input for the next.

Phase 1: Research

Extract curriculum content from the DT4HVE guidance layer and method-tier instructions.

Source Material: DT methodology knowledge — #file:.github/instructions/prompt-builder.instructions.md for authoring standards, the DT4HVE guidance layer for curriculum source content, and the method-tier instruction files (e.g., #file:.github/instructions/dt-method-01-scoping.instructions.md) for practitioner framing to transform into teaching framing.

Steps:

1. Type /clear to start a fresh conversation.
2. Attach #file:.github/instructions/prompt-builder.instructions.md and one or more method-tier instruction files.
3. Copy the prompt below into chat and send.

/task-research topic="DT curriculum instruction files"

Research the DT4HVE guidance layer and method-tier instructions to extract
curriculum content for teaching modules.

Using the attached files, extract:
- Method-tier instruction structure and content for each DT method
- Key concepts, techniques, and vocabulary per method
- Practitioner framing that needs transformation into teaching framing
- Assessment and comprehension check opportunities per method
- Practice exercise material from the manufacturing reference scenario (#618)
- Prompt-builder compliance requirements for .instructions.md files

Output: DT curriculum research

Phase 2: Plan

Plan all 9 curriculum files with consistent structure and progressive complexity.

Steps:

1. Type /clear to reset the conversation.
2. Attach the research document from Phase 1.
3. Copy the prompt below into chat and send.

/task-plan

Plan the 9 DT curriculum instruction files.

Use the attached research document as input. The plan should cover:
- Consistent section structure across all 9 files (overview, key concepts,
  techniques, comprehension checks, practice exercises, learner level adaptations)
- Key concepts and vocabulary for each method
- 3-5 comprehension checks per module (conceptual, scenario-based, progressive)
- Practice exercises referencing the manufacturing scenario
- Learner level adaptations (beginner/intermediate/advanced)
- Token budget per file (~1,000-1,500)
- Continuity across modules (earlier modules simpler, later modules connect
  across methods)

Output: .copilot-tracking/plans/{date}-dt-curriculum-plan.md

Phase 3: Build

Author all 9 curriculum instruction files using prompt-builder.

Steps:

1. Type /clear to reset the conversation.
2. Attach the plan document from Phase 2.
3. Copy the prompt below into chat and send.

/prompt-build

Build the 9 DT curriculum instruction files following the attached plan.

Create .github/instructions/dt-curriculum-{01..09}-*.instructions.md with:
- Frontmatter: description, applyTo targeting curriculum artifact paths
- Module overview in teaching voice (explaining, not facilitating)
- Key concepts with term, definition, relevance, and common misconception
- Techniques explained for learning (what, when, how, good output, pitfalls)
- 3-5 comprehension checks (conceptual, scenario-based, progressive)
- Practice exercises referencing the manufacturing scenario
- Learner level adaptations for all three levels

Maintain consistent structure across files while varying content with method.
Teaching voice throughout — explain concepts, don't prescribe actions.

Output: 9 files at .github/instructions/dt-curriculum-*.instructions.md

Phase 4: Review

Validate curriculum coverage, progressive complexity, and prompt-builder compliance.

Steps:

1. Type /clear to reset the conversation.
2. Attach the plan document from Phase 2.
3. Copy the prompt below into chat and send.

/task-review

Review the 9 DT curriculum instruction files against the attached plan.

Validate:
- All 9 files created with correct frontmatter (description, applyTo)
- Consistent section structure across all files
- Teaching voice distinct from coach facilitation voice
- Key concepts include term, definition, relevance, and common misconception
- Comprehension checks are conceptual, scenario-based, and progressive
- Practice exercises reference the manufacturing scenario
- Learner level adaptations cover all three levels
- Token count per file within ~1,000-1,500 target
- Prompt-builder compliance verified

Output: .copilot-tracking/reviews/{date}-dt-curriculum-review.md

After Review

• Pass — Open a PR with the 9 curriculum files.
• Iterate — Return to Phase 3 with the review document to fix identified issues.
• Escalate — Return to Phase 1 to investigate DT4HVE source content gaps.

Authoring Standards

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

• applyTo targets curriculum artifact paths
• Consistent section structure across all 9 files
• Teaching voice distinct from the coach's facilitation voice
• Token budget per file: ~1,000-1,500

Success Criteria

• 9 curriculum instruction files created (one per DT method)
• Each file has correct frontmatter with description and applyTo
• Module overview explains method purpose in teaching voice
• Key concepts include term, definition, relevance, and common misconception
• Techniques explained for learning (not just doing)
• 3-5 comprehension checks per module — conceptual and scenario-based
• Practice exercises reference the manufacturing scenario
• Learner level adaptations documented for all three levels
• Token count per file within ~1,000-1,500 target
• Passes task-reviewer validation against prompt-builder standards
• Each prompt, instructions, or agent file registered in collections/design-thinking.collection.yml with path and kind fields
• Each prompt, instructions, or agent file registered in collections/hve-core-all.collection.yml with path and kind fields
• npm run plugin:generate succeeds after collection manifest updates