Overview

Create collections/design-thinking.collection.md — the human-readable documentation for the Design Thinking collection. This file appears alongside the manifest and serves as the entry point for users discovering the collection. It explains what the collection provides, how to get started, and documents the full artifact inventory with purpose descriptions.

Target File

collections/design-thinking.collection.md

Required Content

Follow the companion documentation pattern established by existing collection docs (e.g., rpi.collection.md, ado.collection.md). Companion docs are descriptive markdown files with no frontmatter — a narrative overview followed by categorized bullet lists.

Collection Description

Opening paragraphs that explain:

• What the collection provides — an AI-assisted Design Thinking coach and learning tutor covering 9 methodology steps from problem scoping through implementation handoff
• Architecture — single coach agent with tiered instruction modules (ambient personality, method-level knowledge loaded on demand, deep-dive content for advanced users)
• Who benefits — product managers, designers, engineers, and cross-functional teams applying structured innovation methods

Artifact Summary

Categorized bullet lists describing what the collection includes:

• DT Coach — Primary facilitator that guides users through all 9 Design Thinking methods, producing project artifacts in .copilot-tracking/dt/{project-slug}/
• Learning Tutor — Structured curriculum with assessment and adaptive learning for users new to Design Thinking
• Coaching Identity — Ambient instruction defining the Think/Speak/Empower philosophy and progressive hint engine
• Project Conventions — Project structure, artifact naming, and checkpoint patterns
• Method Instructions (1-9) — Method-tier knowledge modules loaded contextually per active method
• Curriculum Content — Teaching modules with comprehension checks and practice exercises
• Method Router — Prompt for navigating between methods based on current project state

How to Build This File

This is a .collection.md companion doc — use the task-implementor agent (not prompt-builder) for the authoring phase.

Workflow: /task-research → /task-plan → /task-implement → /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

Gather structural patterns and tone from existing companion docs.

Source Material: Existing companion docs — rpi.collection.md and ado.collection.md for format conventions. The design-thinking.collection.yml manifest for artifact inventory.

Steps:

1. Type /clear to start a fresh conversation.
2. Attach #file:collections/rpi.collection.md, #file:collections/ado.collection.md, and #file:collections/design-thinking.collection.yml as context.
3. Copy the prompt below into chat and send.

/task-research topic="Design Thinking collection companion doc"

Research the companion documentation format for collection .md files.

Using the attached companion docs as references, extract:
- Document structure (no frontmatter, narrative overview, categorized bullet lists)
- Writing tone and style patterns
- How artifacts are described and categorized
- Level of detail per artifact entry

Then inventory all artifacts from the attached design-thinking.collection.yml
to determine what needs documenting.

Output: DT collection doc research

Phase 2: Plan

Plan the companion doc content and structure.

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 implementation of collections/design-thinking.collection.md.

Use the attached research document as input. The plan should cover:
- Opening paragraphs (collection purpose, architecture, audience)
- Categorized bullet lists (agents, instructions, prompts with descriptions)
- Matching the descriptive style from peer companion docs
- No frontmatter — companion docs are plain markdown

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

Phase 3: Implement

Write the companion doc following the established pattern.

Steps:

1. Type /clear to reset the conversation.
2. Attach the plan document from Phase 2 and #file:collections/rpi.collection.md as a formatting reference.
3. Copy the prompt below into chat and send.

/task-implement

Implement collections/design-thinking.collection.md following the attached plan.

Write a companion doc that follows the pattern from rpi.collection.md:
- No frontmatter
- Narrative opening paragraphs describing the collection
- Categorized bullet lists with bold labels for each artifact
- Accessible, action-oriented tone

Ensure every artifact from design-thinking.collection.yml is documented.

Output: collections/design-thinking.collection.md

Phase 4: Review

Validate the companion doc against conventions and completeness.

Steps:

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

/task-review

Review collections/design-thinking.collection.md against the attached plan.

Validate:
- No frontmatter present (matches companion doc convention)
- Every artifact from design-thinking.collection.yml is documented
- Structure matches peer companion docs (rpi.collection.md)
- Writing style follows markdown and writing-style instructions
- npm run lint:md passes

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

After Review

• Pass — Open a PR with the new companion doc.
• Iterate — Return to Phase 3 with the review document to fix identified issues.
• Escalate — Return to Phase 1 to investigate structural gaps.

Authoring Standards

Follow .github/instructions/markdown.instructions.md and .github/instructions/writing-style.instructions.md:

• No frontmatter — companion docs are plain descriptive markdown
• Instructional tone — address the reader as "you"
• Match structural conventions from peer collection docs

Success Criteria

• File created at collections/design-thinking.collection.md
• No frontmatter — matches existing companion doc convention
• Opening paragraphs explain collection purpose, architecture, and audience
• Categorized bullet lists describe agents, instructions, and prompts
• Structure matches the pattern in peer companion docs (rpi.collection.md)
• Passes npm run lint:md validation