Getting Started with HVE Core
You've installed HVE Core. What now?
The honest answer: you can start using agents immediately, and some of them will produce good results right away. But the real power of HVE Core is a methodology called RPI (Research, Plan, Implement) that changes how you collaborate with AI. Instead of asking AI to "write the code," you ask it to research first, plan second, and implement third. The constraint changes everything.
This guide walks you through four steps, each building on the last:
| Step | What You Do | Time |
|---|---|---|
| First Interaction | Talk to an agent, see it respond | 1 min |
| First Research | Use task-researcher on your own codebase | 5 min |
| First Full Workflow | Run a complete Research, Plan, Implement cycle | 15 min |
| Growing with HVE | Progress through four milestones toward independent use | Ongoing |
TIP
Already comfortable with AI-assisted development? Skip to First Full Workflow or try the rpi-agent for autonomous single-session workflows.
Need installation help? See the Installation Guide for all methods, or install the VS Code extension for the quickest path.
Troubleshooting
Installation Issues
Agent not available
- Ensure GitHub Copilot extension is installed and active
- Reload VS Code window:
Ctrl+Shift+P→ "Developer: Reload Window" - Check that hve-core is accessible (cloned or configured correctly)
Copilot not discovering customizations
- For Multi-Root: Ensure you opened the
.code-workspacefile, not just the folder - Verify
chat.agentFilesLocationspoints to the correct path - Check the window title shows the workspace name
Git or clone errors
- Verify Git is installed: run
git --versionin terminal - Check network connectivity to github.com
- See the installation guide for method-specific troubleshooting
Optional Scripts
HVE Core includes utility scripts you may want to copy into your project:
| Script | Purpose |
|---|---|
scripts/linting/Validate-MarkdownFrontmatter.ps1 | Validate markdown frontmatter against JSON schemas |
scripts/linting/Invoke-PSScriptAnalyzer.ps1 | Run PSScriptAnalyzer with project settings |
scripts/security/Test-DependencyPinning.ps1 | Check GitHub Actions for pinned dependencies |
Copy the scripts you need to your project's scripts/ directory and adjust paths as needed.
Next Steps
- Start the journey: Your First Interaction
- Learn the RPI Workflow for complex tasks
- Browse available agents for the full catalog
Design Thinking Path
For projects requiring user-centered requirements discovery before implementation:
- Design Thinking Guide: Start here for DT overview
- Using the DT Coach: Learn to use the dt-coach agent
- DT to RPI Integration: Transition from DT to implementation
See Also
- Installation Guide - Full decision matrix for all installation methods
- MCP Configuration - Configure Model Context Protocol servers
- Role Guides - Find your role-specific guide
🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.