Skip to main content

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

CollectionDescriptionAgentsPromptsInstructionsSkillsMaturityMarketplace
adoManage Azure DevOps work items, monitor builds, create pull requests, and convert requirements documents into structured work item hierarchies2991StableInstall
coding-standardsEnforce language-specific coding conventions and best practices across your projects, with pre-PR code review agents32151StableInstall
data-scienceGenerate data specifications, Jupyter notebooks, and Streamlit dashboards from natural language descriptions63100StableInstall
design-thinkingAI-enhanced design thinking coaching across nine methods213430PreviewInstall
experimentalExperimental and preview artifacts not yet promoted to stable collections3032ExperimentalInstall
githubManage GitHub issue backlogs with agents for discovery, triage, sprint planning, and execution1660StableInstall
gitlabRun GitLab merge request and pipeline workflows through a focused skill package0011StableInstall
hve-coreFlagship collection: RPI (Research, Plan, Implement, Review) workflow for complex tasks with Git workflow prompts171571StableInstall
hve-core-allComplete collection of all artifacts across all domains516310212StableInstall
installerDeploy HVE artifacts across workspace configurations with decision-driven setup0011StableInstall
jiraManage Jira backlogs, plan PRD-driven issue hierarchies, and execute issue operations2461StableInstall
project-planningCreate architecture decision records, requirements documents, and diagrams through guided AI workflows1811200StableInstall
rai-planningAssess AI systems against Responsible AI standards and capture standards-aligned backlog work2380ExperimentalInstall
securitySecurity review, planning, incident response, risk assessment, and vulnerability analysis914195ExperimentalInstall

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/>(221 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"]
RP["rai#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 --> RP
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.


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