Session M5-03: HVE Core: Evidence-led delivery with RPI

Slides in new tab Download PDF

Close slides

Module: Specification-Driven Frameworks

Difficulty: Advanced

Prerequisites: Sessions M1-01 to M1-03, M2-01 to M2-04 and M3-04, or equivalent Copilot and custom-agent experience

Duration: 4 hours (1 hour trainer content, 3 hours lab)

Overview

Use Hypervelocity Engineering (HVE), a structured engineering framework for GitHub Copilot, to take a feature from research to reviewed code. You start with its file-based Research, Plan, Implement, Review (RPI) workflow. Then you add repository instructions, targeted coding standards, and a custom review agent.

Use Product Manager Advisor to test the value and scope of an Engineering Decision API feature. Agile Coach turns the result into an outcome-oriented story with acceptance criteria. Feed those artifacts back into the HVE plan before implementation and review.

Learning outcomes

• Explain HVE's agents, prompts, instructions, and file-as-interface model.
• Run direct HVE Research, Plan, Implement, and Review phases and inspect each .copilot-tracking/ handoff.
• Compare direct RPI phase prompts with the combined /rpi orchestrator and its Follow-up phase.
• Add project context, targeted JavaScript/API standards, and a custom agent with a defined scope.
• Use Product Manager Advisor and Agile Coach to refine value, scope, user story, and acceptance criteria.
• Deliver and review one containerized API slice through the customized HVE workflow.

Delivery boundary

HVE Core is required for the hands-on challenge. Check that the approved HVE Core extension or Copilot CLI plugin exposes the RPI prompts, agents, and customizations before the lab starts. Add the tested HVE version or channel to the Research artifact. If HVE cannot run, learners may inspect trainer-provided HVE artifacts and observe the workflow, but the walkthrough does not count as challenge completion.

Use synthetic records in a sandbox permitted by the customer. Get approval for package downloads. When local downloads are restricted, use existing dependencies and a trainer-managed remote container build.

Keep .copilot-tracking/ local and ignored by Git. Inspect and grade those files directly. The challenge handoff only lists the four phase artifacts and records the final decision, unresolved risks, and next action.

HVE version and references

This session was last checked against HVE Core documentation on September 24, 2026. HVE commands and generated artifacts can change between versions.

• HVE Core repository and framework overview
• Install HVE Core
• RPI workflow overview
• RPI commands
• Why RPI works

Materials

Resource	Location
Trainer guide	trainer-content/
Slides	slides.md
Lab	lab/
Starter brief and project	lab/starter/
Trainer reference solution	lab/solution/
HVE artifact reference	lab/solution/hve-artifacts.md