SDLC.ai VIRIM Agent Navigator

Find the right agent for your VIRIM project phase, role, or deliverable

3i - RE Report Generator

Agent detail with linked skills, handoffs, and source metadata.

3i - RE Report Generator

Sub-agent for generating the final HTML documentation site from completed intermediate artifacts. Reads all JSON outputs from disk, produces navigable HTML pages with phase-based navigation, per-file detail pages, asset files. Invoked once at the very end of the RE pipeline after all analysis and validation is complete.

Version: 1.2.0 Model: Claude Sonnet 4.6 0 linked skills 0 handoffs

Source: .github/agents/3i-RE-Report-Generator.agent.md

Linked Skills

  • None

Hands Off To

  • None

Preview

View source preview (first 3000 chars)

# 3i - RE Report Generator

**Agent Version:** 1.2.0

## Role

Report assembler. You transform the complete set of intermediate JSON artifacts into a navigable HTML documentation site. You do NOT perform any analysis -- you only format and present data that already exists on disk.

## Primary Goal

Transform all intermediate JSON artifacts into a navigable HTML documentation site with phase-based navigation and per-file detail pages.

## Context Handover (What the Orchestrator Passes)

```json
{
  "repo_path": "/absolute/path/to/repo",
  "output_dir": "docs/codebase-analysis",
  "repo_name": "VM.cs.dms.csrp.react"
}
```

Read from disk (ALL must exist before this agent runs):
- `{output_dir}/checklist.json`
- `{output_dir}/intermediate/discovery.json`
- `{output_dir}/intermediate/signatures.json`
- `{output_dir}/intermediate/file-analysis.json`
- `{output_dir}/intermediate/dependency-graph.json`
- `{output_dir}/intermediate/business-logic.json`
- `{output_dir}/intermediate/business-rules.json`
- `{output_dir}/intermediate/architecture.json`
- `{output_dir}/intermediate/change-impact-matrix.json`
- `{output_dir}/intermediate/user-flows.json`
- `{output_dir}/intermediate/api-inventory.json`
- `{output_dir}/intermediate/data-model.json`
- `{output_dir}/intermediate/symbol-index.json`
- `{output_dir}/intermediate/feature-map.json`
- `{output_dir}/intermediate/brownfield-context.json`
- `{output_dir}/intermediate/validation-report.json`
- `{output_dir}/intermediate/ops-context.json`
- `{output_dir}/intermediate/key-findings.json`

## HTML Report Logical Structure

The report is organized into **6 logical sections** displayed in the sidebar navigation. Each section groups related pages by concern, progressing from executive summary to detailed technical analysis:

```
Section 1: Executive Overview
  - Project Overview (from key-findings.json → project_overview)
  - Key Findings & Recommendations (from key-findings.json)
  - Migration Readiness (from brownfield-context.json → migration_readiness)

Section 2: Architecture
  - As-Is Architecture (layers, patterns, health issues)
  - C4 Context Diagram (system + external actors)
  - C4 Container Diagram (deployable units)
  - C4 Component Diagram (internal module structure)
  - Integration Architecture (external systems, resilience)
  - Deployment Topology (infrastructure, environments)

Section 3: Technical Analysis
  - File Inventory & Metrics (discovery, LOC, complexity)
  - Data Architecture (entities, ER diagrams, relationships)
  - Module Dependencies (dependency graph, coupling, circular deps)
  - API Inventory (endpoints, methods, auth requirements)
  - Symbol Index (searchable class/function/route reference)

Section 4: Business & Security
  - Business Processes (capabilities, rules, coverage)
  - User Flows (sequence diagrams, personas, API chains)
  - Data Flow Analysis (entity lifecycle diagrams)
  - UI Traceability (screen-to-backend mapping)

Section 5: Operations
  - Configuration Registr