Collections Overview

How HVE Artifacts Are Organized

HVE distributes agents, prompts, instructions, and skills through collections, which are curated bundles of related artifacts. Each collection targets a specific domain or workflow, so you can install exactly what you need.

Two VS Code Marketplace extensions deliver these collections:

HVE Core All (ise-hve-essentials.hve-core-all)

The complete bundle containing 260 artifacts across all domains. If you want access to everything without choosing individual collections, install this extension. It is the recommended starting point for most users.

HVE Installer (ise-hve-essentials.hve-installer)

A selective deployment tool with 2 artifacts. Rather than installing the full bundle, the installer lets you choose specific collections and deploy them into your workspace. Use the installer when you want fine-grained control over which artifacts are available.

Collection Relationships

Collections are additive, meaning installing multiple collections may include overlapping items, and that is expected. The hve-core-all extension is the superset bundle containing every artifact from every domain collection. Individual collections exist as independent units, so you can also install them separately through the installer.

Items retain their maturity annotations regardless of how they are installed. For example, design-thinking artifacts are marked "preview" even when accessed through the hve-core-all bundle.

The installer enables targeted deployment of specific collections into workspaces without requiring the full bundle. It is a separate tool, not a subset of hve-core-all.

Available Collections

Collection	Description	Agents	Prompts	Instructions	Skills	Maturity	Marketplace
ado	Manage Azure DevOps work items, monitor builds, create pull requests, and convert requirements documents into structured work item hierarchies	2	9	9	1	Stable	Install
coding-standards	Enforce language-specific coding conventions and best practices across your projects, with pre-PR code review agents	12	0	16	4	Stable	Install
data-science	Generate data specifications, Jupyter notebooks, and Streamlit dashboards from natural language descriptions	7	4	6	2	Stable	Install
design-thinking	AI-enhanced design thinking coaching across nine methods	2	15	2	5	Preview	Install
experimental	Experimental and preview artifacts not yet promoted to stable collections	3	2	11	7	Experimental	Install
github	Manage GitHub issue backlogs with agents for discovery, triage, sprint planning, and execution	1	6	7	1	Stable	Install
gitlab	Run GitLab merge request and pipeline workflows through a focused skill package	0	0	1	1	Stable	Install
hve-core	Flagship collection: RPI (Research, Plan, Implement, Review) workflow for complex tasks with Git workflow prompts	26	16	20	6	Stable	Install
hve-core-all	Complete collection of all artifacts across all domains	71	71	71	47	Stable	Install
installer	Deploy HVE artifacts across workspace configurations with decision-driven setup	0	0	1	1	Stable	Install
jira	Manage Jira backlogs, plan PRD-driven issue hierarchies, and execute issue operations	2	5	6	1	Stable	Install
project-planning	Create architecture decision records, requirements documents, and diagrams through guided AI workflows	26	11	27	12	Stable	Install
security	Security review, planning, incident response, risk assessment, and vulnerability analysis	14	15	11	16	Experimental	Install

How Collections Fit Together

The following diagram shows how the domain collections relate to the two marketplace extensions.

graph TD
    HCA["hve#45;core#45;all<br/>(260 artifacts)"]
    INS["installer<br/>(2 artifacts)"]

    ADO["ado"]
    CS["coding#45;standards"]
    DS["data#45;science"]
    DT["design#45;thinking"]
    EXP["experimental"]
    GH["github"]
    GL["gitlab"]
    HC["hve#45;core"]
    JR["jira"]
    PP["project#45;planning"]
    SP["security"]

    HCA --> ADO
    HCA --> CS
    HCA --> DS
    HCA --> DT
    HCA --> EXP
    HCA --> GH
    HCA --> GL
    HCA --> HC
    HCA --> JR
    HCA --> PP
    HCA --> SP

hve-core-all bundles every domain collection into a single extension. The installer operates independently as a deployment tool for selecting and installing individual collections into workspaces.

Choosing Your Path

If you are getting started and want the simplest setup, install hve-core-all. You get every artifact immediately and can explore at your own pace.

If you prefer a leaner workspace or need to standardize which artifacts are available across a team, use the installer to deploy only the collections relevant to your workflow.

TIP

You can always switch later. Start with hve-core-all to explore, then move to the installer approach when you know which collections your team needs.

After Installing a Collection

Once a collection is installed, its artifacts activate automatically:

1. Agents appear in the Copilot Chat agent picker (press Ctrl+. or use the dropdown).
2. Prompts are available as slash commands (type / in Copilot Chat to see them).
3. Instructions apply automatically to matching files based on their applyTo patterns.
4. Skills extend agent capabilities without additional configuration.

To verify installation, open Copilot Chat and check that collection-specific agents appear in the agent picker. For example, installing the hve-core collection adds Task Researcher, Task Planner, Task Implementor, and Memory agents.

To add more collections later, search "HVE" in the VS Code Extensions marketplace or use the selective install commands from the table above.

---

🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.