Issue Description
Labels: enhancement, agents, architecture, documentation, size: medium
Epic: #63 - Engineering Agents Integration
Related Issues: Part of breaking down #63 into focused implementation tasks
Epic Context
This issue is part of the larger Engineering Agents Integration epic (#63), which aims to integrate 6 collaborative engineering agents from the engineering-team-agents repository into HVE Core. The epic provides multi-platform support (GitHub Copilot + Claude Code + AGENTS.md) while enhancing the existing research → plan → implement workflow with quality gates at strategic points.
Overview
Integrate the System Architecture Reviewer agent to create Architecture Decision Records (ADRs) and preserve institutional knowledge after research and before planning.
User Story
As a developer on the HVE Core team, I want automated architecture documentation and decision tracking, so that technical decisions are preserved and new team members don't repeat past mistakes or debates.
Context
- Current Gap: Technical decisions lost over time, architecture debates repeated
- Problem: Institutional knowledge exists only in people's heads, new developers lack context
- Value Add: Zero repeated architecture debates, preserved decision rationale, scalable team knowledge
- Integration Point: Post-research documentation gate, provides context for
@task-planner
Source Repository
Acceptance Criteria
Technical Requirements
- Platform Support: Claude Code, GitHub Copilot (native + chatmodes), universal AGENTS.md
- Documentation Structure:
docs/architecture/ADR-[number]-[title].md
docs/templates/adr-template.md
- Frameworks Applied:
- Microsoft Well-Architected Framework (AI pillars)
- OWASP Top 10 Architecture
- OWASP LLM Security Architecture
- OWASP ML Security Architecture
- Zero Trust principles
- Decision Trees: Database choice, AI architecture, deployment patterns, caching strategies
Implementation Phases
Phase 1: Port Agent
- Adapt system-architecture-reviewer.md from source repository
- Create Claude version (
.claude/agents/)
- Create GitHub native version (
.github/agents/)
- Create GitHub chatmode version (
.github/chatmodes/)
- Add agent to AGENTS.md
Phase 2: Documentation Setup
- Create
docs/architecture/ directory
- Port ADR template
- Add framework reference documentation
- Add cross-references to existing instructions
Phase 3: Integration & Testing
- Test agent in Claude Code
- Test agent in GitHub Copilot
- Validate ADR creation workflow
- Test cross-agent collaboration (Architecture → Code Reviewer)
- Validate backward compatibility
Definition of Done
Dependencies
- None (independent implementation)
Related Documentation
Additional Context
No response
Issue Description
Labels:
enhancement,agents,architecture,documentation,size: mediumEpic: #63 - Engineering Agents Integration
Related Issues: Part of breaking down #63 into focused implementation tasks
Epic Context
This issue is part of the larger Engineering Agents Integration epic (#63), which aims to integrate 6 collaborative engineering agents from the engineering-team-agents repository into HVE Core. The epic provides multi-platform support (GitHub Copilot + Claude Code + AGENTS.md) while enhancing the existing research → plan → implement workflow with quality gates at strategic points.
Overview
Integrate the System Architecture Reviewer agent to create Architecture Decision Records (ADRs) and preserve institutional knowledge after research and before planning.
User Story
As a developer on the HVE Core team, I want automated architecture documentation and decision tracking, so that technical decisions are preserved and new team members don't repeat past mistakes or debates.
Context
@task-plannerSource Repository
Acceptance Criteria
.claude/agents/).github/agents/and.github/chatmodes/)docs/architecture/docs/templates/Technical Requirements
docs/architecture/ADR-[number]-[title].mddocs/templates/adr-template.mdImplementation Phases
Phase 1: Port Agent
.claude/agents/).github/agents/).github/chatmodes/)Phase 2: Documentation Setup
docs/architecture/directoryPhase 3: Integration & Testing
Definition of Done
@task-plannerdocumentedDependencies
Related Documentation
Additional Context
No response