AI-Assisted Project Lifecycle Overview
Overview
HVE Core supports a 9-stage project lifecycle, from initial setup through ongoing operations, with AI-assisted tooling at each stage. Every stage maps to specific agents, prompts, instructions, and skills that accelerate your work and reduce friction. Use this guide to navigate the full lifecycle and find the right tools for your current project phase.
Stage Overview
| Stage | Name | Asset Count | Key Tools | Guide |
|---|---|---|---|---|
| Stage 1 | Setup | 4 | hve-core-installer, memory | Setup |
| Stage 2 | Discovery | 14 | task-researcher, brd-builder, security-plan-creator | Discovery |
| Stage 3 | Product Definition | 6 | prd-builder, product-manager-advisor, adr-creation | Product Definition |
| Stage 4 | Decomposition | 5 | ado-prd-to-wit, github-backlog-manager | Decomposition |
| Stage 5 | Sprint Planning | 9 | github-backlog-manager, agile-coach | Sprint Planning |
| Stage 6 | Implementation | 30 | task-researcher, task-planner, task-implementor, task-reviewer, rpi-agent, prompt-builder | Implementation |
| Stage 7 | Review | 11 | task-reviewer, pr-review | Review |
| Stage 8 | Delivery | 9 | git-merge, ado-get-build-info | Delivery |
| Stage 9 | Operations | 11 | doc-ops, prompt-builder, incident-response | Operations |
Where Are You?
Use this navigator to jump directly to the stage matching your current need.
| I want to... | Start Here |
|---|---|
| Set up HVE Core for the first time | Stage 1: Setup |
| Understand requirements or research a topic | Stage 2: Discovery |
| Create a product spec or architecture decision | Stage 3: Product Definition |
| Break work into tasks or work items | Stage 4: Decomposition |
| Plan a sprint or manage my backlog | Stage 5: Sprint Planning |
| Write code, build features, or create content | Stage 6: Implementation |
| Review code or get PR feedback | Stage 7: Review |
| Merge, release, or deploy | Stage 8: Delivery |
| Monitor, maintain, or respond to incidents | Stage 9: Operations |
Lifecycle Flow
TIP
Design Thinking can feed into this lifecycle at three exit points. See the DT-RPI integration guide for details.
Stage Transition Rules
- Design Thinking Exit 1 to Stage 2: Problem statement complete (Methods 1-3) feeds Task Researcher in Discovery
- Design Thinking Exit 2 to Stage 2: Validated concept (Methods 4-6) feeds Task Researcher in Discovery
- Design Thinking Exit 3 to Stage 2: Implementation spec (Methods 7-9) feeds Task Researcher in Discovery
- Stage 1 to Stage 2: Installation complete
- Stage 2 to Stage 3: BRD complete, handoff at
docs/brds/ - Stage 2 to Stage 4: TPMs skip PRD when BRD is sufficient
- Stage 3 to Stage 4: PRD and ADRs finalized
- Stage 4 to Stage 5: Work items created
- Stage 5 to Stage 6: Sprint planned
- Stage 6 to Stage 7: Implementation complete,
/clearcontext - Stage 7 to Stage 8: PR approved
- Stage 7 to Stage 6: Rework needed
- Stage 8 to Stage 6: Next sprint
- Stage 8 to Stage 9: Final sprint complete
- Stage 9 to Stage 6: Hotfix needed
Coverage Notes
Stage 6 Implementation carries the highest asset density with 30 assets, representing roughly 35% of all stage assignments. Stage 8 Delivery has zero agents and operates entirely through prompts and auto-activated instructions. Stage 1 Setup has minimal coverage with only 4 assets, reflecting its narrow scope as a one-time onboarding step.
Each stage page follows a consistent structure covering purpose, key activities, AI-assisted workflow, and cross-references. This format lets you navigate directly to the stage relevant to your current work and find both manual checklists and AI agent commands. Stages with fewer tools (Stage 1 through Stage 5) use flat tables, while stages with more tools (Stage 6 through Stage 9) use categorized subsections for navigability.
Next Steps
TIP
Find your role-specific guide at Role Guides to see which stages matter most for your work.
🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.