Overview

Update collections/hve-core-all.collection.yml to list all Design Thinking artifacts individually. The hve-core-all manifest uses flat item listings — each artifact appears as its own entry with path and kind fields, following the pattern of existing entries (e.g., RPI, ADO, coding-standards artifacts). Adding these entries ensures users who install the full HVE Core bundle automatically receive all Design Thinking capabilities.

Target Files

• collections/hve-core-all.collection.yml
• collections/hve-core-all.collection.md

Required Changes

Add Design Thinking Artifact Entries

Add individual entries for each Design Thinking artifact to hve-core-all.collection.yml. Each entry uses path and kind fields following the pattern of existing items (e.g., .github/agents/dt-coach.agent.md with kind: agent, .github/instructions/dt-coach-personality.instructions.md with kind: instruction).

Study the existing entries in hve-core-all.collection.yml to match:

• Field names and ordering (path, kind, optional maturity: experimental)
• Path conventions (.github/agents/, .github/instructions/, .github/prompts/)
• Alphabetical placement within the items list

Companion Documentation Update

Update collections/hve-core-all.collection.md to document the Design Thinking artifacts. Add a section describing what the DT collection provides, following the existing companion doc pattern.

How to Build This File

This is a YAML manifest update — 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

Study the meta-collection manifest and the DT collection to identify all artifacts.

Source Material: Meta-collection structure — #file:collections/hve-core-all.collection.yml for the item listing pattern, #file:collections/hve-core-all.collection.md for companion documentation, and #file:collections/design-thinking.collection.yml for the list of DT artifacts.

Steps:

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

/task-research topic="hve-core-all DT integration"

Research the meta-collection manifest structure for integrating Design Thinking
artifacts.

Using the attached files, extract:
- Item listing pattern in hve-core-all.collection.yml (path + kind fields)
- How existing collections' artifacts appear as individual entries
- Companion documentation structure in hve-core-all.collection.md
- Complete list of DT artifacts from design-thinking.collection.yml that need
  individual entries
- Any maturity or display metadata conventions

Output: DT metacollection research

Phase 2: Plan

Plan the YAML entries and companion doc updates.

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 hve-core-all integration for Design Thinking artifacts.

Use the attached research document as input. The plan should cover:
- Individual item entries for each DT artifact (path + kind for each)
- Alphabetical placement within the existing items list
- Whether maturity: experimental is appropriate for new entries
- Companion documentation additions (new DT section)
- Validation commands (npm run plugin:generate, npm run lint:yaml)

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

Phase 3: Implement

Add the individual DT artifact entries and update the companion doc.

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-implement

Implement the hve-core-all integration following the attached plan.

Add individual entries for each Design Thinking artifact to
collections/hve-core-all.collection.yml using path + kind fields. Place entries
alphabetically within the items list.

Update collections/hve-core-all.collection.md to document the DT artifacts
following the existing companion doc pattern.

After changes, run:
- npm run plugin:generate
- npm run lint:yaml

Output: Updated collections/hve-core-all.collection.yml and collections/hve-core-all.collection.md

Phase 4: Review

Validate the integration is correct and complete.

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 hve-core-all DT integration against the attached plan.

Validate:
- All DT artifacts from design-thinking.collection.yml have individual entries
- Each entry uses path + kind fields matching the existing pattern
- Entries are alphabetically placed
- No dependency-style or collection-reference entries were used
- Companion doc accurately describes the DT artifacts
- npm run plugin:generate succeeds
- npm run lint:yaml passes

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

After Review

• Pass — Open a PR with the integration changes.
• Iterate — Return to Phase 3 with the review document to fix identified issues.
• Escalate — Return to Phase 1 to investigate meta-collection conventions.

Authoring Standards

Follow existing meta-collection conventions:

• Match the item entry format from peer entries (path + kind)
• Use consistent YAML formatting
• Documentation updates follow markdown and writing-style instructions

Success Criteria

• All Design Thinking artifacts added individually to collections/hve-core-all.collection.yml with path and kind fields
• Entries follow the pattern of existing items (field names, ordering, path conventions)
• collections/hve-core-all.collection.md updated to document the DT artifacts
• npm run plugin:generate succeeds with the updated manifest
• npm run lint:yaml passes