microsoft/hve-core

Public

mirrored fromhttps://github.com/microsoft/hve-coreAvailable

CodeCommitsIssuesPull requestsActionsInsightsSecurity
1a96b7384cd85a53b6036e7275d391fcb75cd11d

Branches

Tags

  • No tags available.
0Branches0Tags
Go to file
Add file
Code

Clone

HTTPS

Download ZIP

docs/getting-started/install.md

247lines · modecode

1---
2title: Installing HVE-Core
3description: Choose the right installation method for your environment
4sidebar_position: 2
5author: Microsoft
6ms.date: 2025-12-02
7ms.topic: how-to
8keywords:
9 - installation
10 - setup
11 - github copilot
12 - devcontainer
13 - codespaces
14estimated_reading_time: 5
15---
16
17HVE-Core provides GitHub Copilot customizations (custom agents, instructions, and prompts) that enhance your development workflow. This guide helps you choose the right installation method for your environment.
18
19## Recommended: VS Code Extension ⭐
20
21**For most users**, the simplest method is to install directly from the VS Code Marketplace:
22
23```text
24VS Code → Extensions → Search "HVE Core" → Install
25```
26
27**Or visit:** [HVE Core on Marketplace](https://marketplace.visualstudio.com/items?itemName=ise-hve-essentials.hve-core)
28
29### Why choose the extension
30
31* ✅ Zero configuration required
32* ✅ Automatic updates via VS Code
33* ✅ Works everywhere (local, devcontainers, Codespaces)
34* ✅ No project files needed
35* ✅ Instant availability
36
37### When to use alternatives
38
39* ❌ You need to customize components → Use custom installation methods below
40* ❌ Team needs version control → Use [Submodule](methods/submodule.md)
41* ❌ Contributing to HVE-Core → Use [Peer Clone](methods/peer-clone.md)
42
43See [Extension Installation Guide](methods/extension.md) for complete documentation.
44
45## Custom Installation Methods
46
47If you need customization or version control of HVE-Core, choose from the methods below.
48
49## Quick Start
50
51> **Starter prompt:** "Help me choose how to install this library"
52
53Open Copilot Chat, select the `hve-core-installer` agent, and use this prompt. The agent will ask three questions about your environment and recommend the best method.
54
55## Help Me Choose
56
57Answer these questions to find your recommended installation method:
58
591. What's your development environment?
60 * Local VS Code (no devcontainer)
61 * Local devcontainer (Docker Desktop)
62 * GitHub Codespaces
63 * Both local and Codespaces
64
652. Solo or team development?
66 * Solo: Just you, no version control of HVE-Core needed
67 * Team: Multiple people, need reproducible setup
68
693. Update preference?
70 * Auto: Always get latest HVE-Core
71 * Controlled: Pin to specific version, update explicitly
72
73### Decision Matrix
74
75| Environment | Team | Updates | Recommended Method |
76|---------------------------|------|------------|-----------------------------------------------|
77| **Any** (simplest) | Any | Auto | [VS Code Extension](methods/extension.md) ⭐ |
78| Local (no container) | Solo | Manual | [Peer Directory Clone](methods/peer-clone.md) |
79| Local (no container) | Team | Controlled | [Submodule](methods/submodule.md) |
80| Local devcontainer | Solo | Auto | [Git-Ignored Folder](methods/git-ignored.md) |
81| Local devcontainer | Team | Controlled | [Submodule](methods/submodule.md) |
82| Codespaces only | Solo | Auto | [GitHub Codespaces](methods/codespaces.md) |
83| Codespaces only | Team | Controlled | [Submodule](methods/submodule.md) |
84| Both local + Codespaces | Any | Any | [Multi-Root Workspace](methods/multi-root.md) |
85| Advanced (shared install) | Solo | Auto | [Mounted Directory](methods/mounted.md) |
86
87⭐ **VS Code Extension** is the recommended method for most users who don't need customization.
88
89## Collection Packages
90
91HVE-Core organizes artifacts into role-based collections. The VS Code extension installs the **Full** collection. Clone-based methods let you select any collection during setup.
92
93| Collection | Collection ID | Maturity | Description |
94|-------------------|---------------------|--------------|------------------------------------------------------------------|
95| **Full** ⭐ | `hve-core-all` | Stable | All stable artifacts (recommended for most) |
96| HVE Core Workflow | `hve-core` | Stable | RPI workflow with Git commit, merge, and pull request prompts |
97| Azure DevOps | `ado` | Stable | Work item management, build monitoring, and PR creation |
98| Coding Standards | `coding-standards` | Stable | Language-specific instructions for bash, Bicep, C#, Python, etc. |
99| Data Science | `data-science` | Stable | Data specs, Jupyter notebooks, and Streamlit dashboards |
100| Design Thinking | `design-thinking` | Preview | AI-enhanced Design Thinking coaching across nine methods |
101| GitHub Backlog | `github` | Stable | Issue discovery, triage, sprint planning, and backlog execution |
102| Installer | `installer` | Stable | Interactive installer agent for workspace configuration |
103| Project Planning | `project-planning` | Stable | PRDs, BRDs, ADRs, and architecture diagrams |
104| Security Planning | `security-planning` | Stable | Security plans, incident response, and risk assessment |
105| Experimental | `experimental` | Experimental | Artifacts not yet promoted to stable collections |
106
107### Extension Installation (Full Collection)
108
109The VS Code Marketplace extension installs the **Full** collection containing all stable artifacts. This is the recommended approach for most users.
110
111### Clone Methods (Collection Filtering)
112
113Clone-based installation methods support collection-based agent filtering through the installer agent:
114
1151. Clone the repository using your preferred method
1162. Run the `hve-core-installer` agent
1173. In Phase 7 (Agent Customization), select your role-based collection or install all agents
118
119The installer reads collection assignments from the collection manifests (`collections/*.collection.yml`) and copies only the agents assigned to your selected collection. Agents marked for all collections are always included.
120
121> [!NOTE]
122> Collection filtering applies to agents only. Copying of related prompts, instructions, and skills based on collection is planned for a future release.
123
124### Quick Decision Tree
125
126```text
127┌─────────────────────────────────────────────────────────────────┐
128│ │
129│ Want the simplest setup? │
130│ └─ Yes ──────────────────────────────► VS Code Extension ⭐ │
131│ │
132│ Need to customize HVE-Core? │
133│ ├─ Local VS Code only ──────────────► Peer Directory Clone │
134│ ├─ Local devcontainer only ─────────► Git-Ignored Folder │
135│ ├─ Codespaces only ─────────────────► GitHub Codespaces │
136│ └─ Both local + Codespaces ─────────► Multi-Root Workspace │
137│ │
138│ Working in a team? │
139│ └─ Yes, need version control ───────► Submodule │
140│ │
141└─────────────────────────────────────────────────────────────────┘
142```
143
144## Installation Methods
145
146### Simplest Method (Recommended for Most Users)
147
148| Method | Best For | Complexity |
149|---------------------------------------------|----------------------------------|------------|
150| [VS Code Extension](methods/extension.md) ⭐ | Anyone wanting zero-config setup | Minimal |
151
152### Consumer Methods (Customization + Version Control)
153
154These methods are for projects that want to use and potentially customize HVE-Core's components:
155
156| Method | Best For | Complexity |
157|-----------------------------------------------|-------------------------------|------------|
158| [Multi-Root Workspace](methods/multi-root.md) | Any environment, portable | Low |
159| [Submodule](methods/submodule.md) | Teams needing version control | Medium |
160
161### Developer Methods
162
163These methods are for HVE-Core contributors or advanced scenarios:
164
165| Method | Best For | Complexity |
166|-----------------------------------------------|-------------------------------|------------|
167| [Peer Directory Clone](methods/peer-clone.md) | Local VS Code, solo | Low |
168| [Git-Ignored Folder](methods/git-ignored.md) | Local devcontainer, solo | Low |
169| [Mounted Directory](methods/mounted.md) | Advanced devcontainer sharing | High |
170| [GitHub Codespaces](methods/codespaces.md) | Codespaces-only projects | Medium |
171
172## Using the Installer Agent
173
174The `hve-core-installer` agent automates any installation method:
175
1761. Open GitHub Copilot Chat in VS Code (`Ctrl+Alt+I`)
1772. Select `hve-core-installer` from the agent picker
1783. Answer the environment detection questions
1794. The agent executes your chosen method
180
181The agent handles:
182
183* Environment detection (Local VS Code, Devcontainer, Codespaces)
184* Repository cloning or configuration
185* VS Code settings updates
186* Devcontainer configuration
187* Validation of the installation
188
189## Validation
190
191After installation, verify everything works:
192
1931. Open GitHub Copilot Chat (`Ctrl+Alt+I`)
1942. Click the agent picker dropdown
1953. Verify HVE-Core agents appear (task-planner, task-researcher, prompt-builder)
1964. Select an agent and submit a test prompt
197
198Run the installer in validation mode:
199
200> "Validate my HVE-Core installation"
201
202## Post-Installation: Update Your .gitignore
203
204HVE-Core agents create ephemeral workflow artifacts in a `.copilot-tracking/` folder within your project. These files include research documents, implementation plans, PR review tracking, and other machine-generated content that should typically not be committed to version control.
205
206### Add this line to your project's `.gitignore`
207
208```text
209.copilot-tracking/
210```
211
212> [!IMPORTANT]
213> This applies to all installation methods (extension, submodule, peer clone, etc.). The `.copilot-tracking/` folder is created in your project directory, not in HVE-Core itself.
214
215### What gets stored there
216
217* Research documents from `task-researcher`
218* Implementation plans from `task-planner`
219* PR review artifacts from `pr-review`
220* Work item planning files for ADO workflows
221* Temporary prompt files used by agents
222
223These artifacts are useful during your workflow session but are ephemeral by design. They help agents maintain context across sessions without polluting your repository history.
224
225## MCP Server Configuration (Optional)
226
227Some HVE-Core agents use MCP (Model Context Protocol) servers to integrate with Azure DevOps, GitHub, or documentation services. These are optional enhancements; agents work without MCP configuration.
228
229If you use agents like `ado-prd-to-wit` or `github-backlog-manager`, see [MCP Server Configuration](mcp-configuration.md) for setup instructions. That guide includes:
230
231* Which agents require which MCP servers
232* Complete configuration templates
233* Method-specific placement notes (extension, submodule, Codespaces, etc.)
234* Troubleshooting for common issues
235
236## Next Steps
237
238* [Your First Workflow](first-workflow.md) - Try HVE-Core with a real task
239* [RPI Workflow](../rpi/) - Research, Plan, Implement methodology
240* [Contributing](../contributing/) - Contribute to HVE-Core
241
242---
243
244<!-- markdownlint-disable MD036 -->
245*🤖 Crafted with precision by ✨Copilot following brilliant human instruction,
246then carefully refined by our team of discerning human reviewers.*
247<!-- markdownlint-enable MD036 -->
248