microsoft/hve-core
Publicmirrored fromhttps://github.com/microsoft/hve-coreAvailable
docs/contributing/ROADMAP.md
202lines · modecode
| 1 | --- |
| 2 | title: Roadmap |
| 3 | description: Project direction and priorities for HVE Core over the next 12-18 months |
| 4 | author: HVE Core Team |
| 5 | ms.date: 2026-01-21 |
| 6 | ms.topic: reference |
| 7 | keywords: |
| 8 | - roadmap |
| 9 | - project direction |
| 10 | - priorities |
| 11 | - AI coding agents |
| 12 | - github copilot |
| 13 | estimated_reading_time: 8 |
| 14 | --- |
| 15 | |
| 16 | ## Overview |
| 17 | |
| 18 | HVE Core intends to accelerate Azure solution development over the next 12-18 months by providing optimized GitHub Copilot customizations (agents, instructions, and prompts) that transform AI coding assistants from suggestion engines into reliable engineering partners. The RPI (Research, Plan, Implement) framework remains central to this vision, ensuring AI produces verified, context-aware code rather than plausible-looking hallucinations. |
| 19 | |
| 20 | Actual delivery may vary based on contributor availability, community feedback, and evolving AI capabilities. |
| 21 | |
| 22 | ## Current State (January 2026) |
| 23 | |
| 24 | HVE Core v1.1.0 provides: |
| 25 | |
| 26 | * Task researcher, planner, and implementor agents for structured AI workflows (RPI Framework) |
| 27 | * Marketplace distribution via VS Code extension for zero-configuration setup |
| 28 | * 15+ specialized agents for BRD building, architecture diagrams, issue management, and more |
| 29 | * 20+ instruction files covering C#, Terraform, Bicep, Python, bash, and prompt engineering |
| 30 | * Git workflow prompts, ADR planning, risk registers, and PR creation templates |
| 31 | * Frontmatter validation, markdown linting, security scanning, and dependency pinning tooling |
| 32 | * Pre-configured DevContainer with all required development tools |
| 33 | |
| 34 | ## Priorities for 2026-2027 |
| 35 | |
| 36 | ### Agent Framework Evolution |
| 37 | |
| 38 | **Will Do:** |
| 39 | |
| 40 | * Expand MCP (Model Context Protocol) integration for standardized tool connections |
| 41 | * Develop multi-agent coordination patterns for complex enterprise scenarios |
| 42 | * Create specialized agents for Azure service categories (compute, data, AI/ML, security) |
| 43 | * Build agent composition patterns allowing agents to delegate to specialized sub-agents |
| 44 | * Add agent metrics and observability for understanding AI decision patterns |
| 45 | * Implement agent memory and context management capabilities |
| 46 | |
| 47 | **Won't Do:** |
| 48 | |
| 49 | * Build a custom orchestration runtime; use LangGraph or similar established frameworks instead |
| 50 | * Create proprietary tool protocols that compete with MCP |
| 51 | * Develop agents for non-Azure cloud providers (AWS, GCP) in this repository |
| 52 | |
| 53 | ### Instructions Expansion |
| 54 | |
| 55 | **Will Do:** |
| 56 | |
| 57 | * Add instructions for emerging Azure services (Azure AI Foundry, Azure Container Apps) |
| 58 | * Create security-focused instructions for threat modeling and secure coding patterns |
| 59 | * Develop instructions for infrastructure-as-code testing (Terratest, Bicep testing) |
| 60 | * Build instructions for observability implementation (Azure Monitor, Application Insights) |
| 61 | * Enhance existing C# instructions with .NET 9+ patterns and minimal API guidance |
| 62 | * Add instructions for GitHub Actions workflow authoring |
| 63 | |
| 64 | **Won't Do:** |
| 65 | |
| 66 | * Create instructions for out-of-market Azure services |
| 67 | * Maintain instructions for non-Microsoft technology stacks unless directly relevant to Azure integration |
| 68 | * Build framework-specific instructions for every JavaScript/Python framework |
| 69 | |
| 70 | ### Prompt Engineering |
| 71 | |
| 72 | **Will Do:** |
| 73 | |
| 74 | * Develop prompt templates for common Azure architecture patterns (hub-spoke, landing zones) |
| 75 | * Create code review prompts that understand Azure Well-Architected & Cloud-Adoption Framework principles |
| 76 | * Add incident response prompts for Azure operations scenarios |
| 77 | * Develop security audit prompts for Azure resource configurations |
| 78 | |
| 79 | **Won't Do:** |
| 80 | |
| 81 | * Create prompts for general-purpose coding tasks without Azure context |
| 82 | * Build prompts that duplicate functionality available in GitHub Copilot's native capabilities |
| 83 | |
| 84 | ### Enterprise Readiness |
| 85 | |
| 86 | **Will Do:** |
| 87 | |
| 88 | * Document governance patterns for organization-wide Hypervelocity Engineering adoption |
| 89 | * Create compliance mapping for Azure Policy and Defender for Cloud alignment |
| 90 | * Build audit logging recommendations for AI-assisted code changes |
| 91 | * Develop approval workflow patterns for high-risk AI operations |
| 92 | * Add data classification guidance for sensitive context handling |
| 93 | |
| 94 | **Won't Do:** |
| 95 | |
| 96 | * Build enterprise licensing or access control systems |
| 97 | * Create centralized management infrastructure; organizations should use existing policy mechanisms |
| 98 | |
| 99 | ### Documentation and Learning |
| 100 | |
| 101 | **Will Do:** |
| 102 | |
| 103 | * Create video tutorials demonstrating RPI workflow with real Azure projects |
| 104 | * Develop scenario-based guides (greenfield, modernization, migration) |
| 105 | * Build troubleshooting guides for common AI coding assistant issues |
| 106 | * Add architecture decision records (ADRs) explaining design choices |
| 107 | * Create certification-style learning paths for HVE Core proficiency |
| 108 | |
| 109 | **Won't Do:** |
| 110 | |
| 111 | * Duplicate Azure documentation: link to authoritative sources instead |
| 112 | * Create marketing materials or promotional content |
| 113 | |
| 114 | ### Community and Ecosystem |
| 115 | |
| 116 | **Will Do:** |
| 117 | |
| 118 | * Establish contribution guidelines for new agents and instructions |
| 119 | * Create agent and instruction quality criteria for inclusion |
| 120 | * Build automated testing for agent and instruction effectiveness |
| 121 | * Develop community showcase for organization-specific customizations |
| 122 | * Add integration guides for popular Azure development tools |
| 123 | |
| 124 | **Won't Do:** |
| 125 | |
| 126 | * Accept agents or instructions that don't align with project scope |
| 127 | * Maintain community contributions without active maintainers |
| 128 | * Build a separate community platform; use GitHub Discussions and Issues |
| 129 | |
| 130 | ## Out of Scope |
| 131 | |
| 132 | The following areas are explicitly out of scope for HVE Core: |
| 133 | |
| 134 | * Non-Azure cloud providers (AWS, GCP customizations belong in separate projects) |
| 135 | * General-purpose coding assistance (use GitHub Copilot's native capabilities for non-Azure-specific tasks) |
| 136 | * Model training or fine-tuning (HVE Core uses prompt engineering, not model customization) |
| 137 | * IDE plugins beyond VS Code (the VS Code extension is the primary distribution mechanism) |
| 138 | * Proprietary or closed-source components (all HVE Core code remains MIT-licensed open source) |
| 139 | * Runtime infrastructure (no backend services, APIs, or hosted components) |
| 140 | * Language model hosting (HVE Core works with existing Copilot infrastructure) |
| 141 | |
| 142 | ## Success Metrics |
| 143 | |
| 144 | Progress is measured by: |
| 145 | |
| 146 | | Metric | Target | Rationale | |
| 147 | |----------------------------|----------------------------------------|-----------------------------------------------| |
| 148 | | Agent coverage | 25+ agents | Cover common Azure development scenarios | |
| 149 | | Instruction coverage | 35+ instructions | Address major Azure technologies and patterns | |
| 150 | | VS Code extension installs | 10,000+ | Validate community adoption | |
| 151 | | GitHub stars | 500+ | Measure community interest | |
| 152 | | Active contributors | 10+ | Ensure project sustainability | |
| 153 | | Issue response time | < 7 days | Maintain community engagement | |
| 154 | | Documentation completeness | 100% of agents/instructions documented | Enable self-service adoption | |
| 155 | |
| 156 | ## Timeline Overview |
| 157 | |
| 158 | ```text |
| 159 | Q1 2026 (Current) |
| 160 | ├── MCP integration groundwork |
| 161 | ├── Agent metrics foundation |
| 162 | └── Security-focused instructions |
| 163 | |
| 164 | Q2 2026 |
| 165 | ├── Multi-agent coordination patterns |
| 166 | ├── Azure AI Foundry agents |
| 167 | └── Video tutorial series launch |
| 168 | |
| 169 | Q3 2026 |
| 170 | ├── Enterprise governance documentation |
| 171 | ├── Migration prompt templates |
| 172 | └── Community contribution framework |
| 173 | |
| 174 | Q4 2026 |
| 175 | ├── Agent composition patterns |
| 176 | ├── Certification learning paths |
| 177 | └── Automated effectiveness testing |
| 178 | |
| 179 | Q1 2027 |
| 180 | ├── Agent memory capabilities |
| 181 | ├── Architecture pattern prompts |
| 182 | └── Compliance mapping documentation |
| 183 | ``` |
| 184 | |
| 185 | ## How to Influence the Roadmap |
| 186 | |
| 187 | The roadmap evolves based on community input: |
| 188 | |
| 189 | * Open a [GitHub Issue](https://github.com/microsoft/hve-core/issues) with the `enhancement` label for feature requests |
| 190 | * Join [GitHub Discussions](https://github.com/microsoft/hve-core/discussions) to propose and debate priorities |
| 191 | * Submit PRs for items on the roadmap; early contributors shape implementation direction |
| 192 | * Use agents and instructions in real projects and report what works and what doesn't |
| 193 | |
| 194 | ## Version History |
| 195 | |
| 196 | | Version | Date | Changes | |
| 197 | |---------|------------|-----------------------------| |
| 198 | | 1.0 | 2026-01-21 | Initial roadmap publication | |
| 199 | |
| 200 | *This roadmap satisfies OpenSSF Best Practices Badge Silver criterion `documentation_roadmap`.* |
| 201 | |
| 202 | 🤖 *Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.* |
| 203 | |