dt-coaching-foundation
Design Thinking coaching foundation knowledge: coach identity and philosophy, quality and fidelity constraints, method sequencing, coaching state schema, and the canonical deck workflow
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 355
01 前言 Front Matter
- name
- dt-coaching-foundation
- metadata
- { "authors": "microsoft/hve-core", "last_updated": "2026-10-02" }
- description
- Design Thinking coaching foundation knowledge: coach identity and philosophy, quality and fidelity constraints, method sequencing, coaching state schema, and the canonical deck workflow
- user-invocable
- false
02 资源文件 5
- 参考文档references/canonical-deck.md12.5 KB
- 参考文档references/coaching-identity.md3.9 KB
- 参考文档references/coaching-state.md11.0 KB
- 参考文档references/method-sequencing.md6.6 KB
- 参考文档references/quality-constraints.md3.5 KB
03 SKILL.md 正文
DT Coaching Foundation — Skill Entry
This SKILL.md is the entrypoint for the Design Thinking coaching foundation knowledge.
The dt-coach agent loads this skill at session start and during a coaching session to ground coaching behavior in a stable identity, enforce quality and fidelity expectations, navigate method transitions, persist and recover session state, and run the opt-in canonical deck workflow. The foundation knowledge stays constant across all nine Design Thinking methods.
Foundation references
Load the reference that matches the current coaching moment.
| Reference | When to load |
|---|---|
| coaching-identity.md | At session start and throughout — establishes coach identity, Think/Speak/Empower philosophy, boundaries, and the Progressive Hint Engine. |
| quality-constraints.md | Before any artifact generation — enforces fidelity rules, anti-polish stance, and quality-by-space expectations. |
| method-sequencing.md | At method transitions, space boundaries, and when the team asks what to do next — guides the nine-method sequence, transition protocol, next-method assessment, and non-linear iteration. |
| coaching-state.md | For persistence and session recovery — defines the coaching state schema, update rules, and recovery protocol. |
| canonical-deck.md | For opt-in canonical deck and customer-card generation — governs activation, offer points, and the customer-card branch. |
Skill layout
SKILL.md— this file (skill entrypoint).references/— the DT coaching foundation knowledge documents.coaching-identity.md— coach identity, philosophy, and interaction conventions.quality-constraints.md— fidelity rules and quality standards across all methods.method-sequencing.md— method transitions, space boundaries, next-method assessment, and iteration patterns.coaching-state.md— coaching state schema, file conventions, and recovery protocol.canonical-deck.md— opt-in canonical deck and customer-card workflow.
04 同仓库更多 Skills
statistical-hypothesis-testing
Compare binary rates or average values across affected and unaffected cohorts during root cause analysis. Use when root-cause-analysis selects an applicable affected-versus-unaffected cohort comparison.
root-cause-analysis
Investigate incidents, software defects, and data or process failures by forming falsifiable hypotheses, executing tests against available evidence, and iterating to a verified causal explanation or an explicit evidence blocker. Use when performing root cause analysis, incident investigation, or postmortem analysis, with cost and model choice confirmed before a full investigation.
causal-evidence-likelihood
Assess how one evidence item changes an RCA hypothesis using an uncalibrated, model-elicited likelihood-ratio band. Use when root-cause-analysis selects an eligible hypothesis-evidence pair.
untrusted-content-boundary
Untrusted-content boundary: treat ingested external content as data, not instructions, and refuse embedded authority changes. Preloaded by agents that read external, tracker, or user-supplied content.
telemetry-foundations
Declarative OpenTelemetry-aligned telemetry vocabulary and instrumentation conventions for traces, metrics, logs, and PII handling
pr-reference
Generates PR reference XML with commit history and unified diffs between branches, with extension and path filtering. Use when creating pull request descriptions, preparing code reviews, analyzing branch changes, discovering work items from diffs, or generating structured diff summaries.