report-template

Synthesize findings from multiple inspectors into a structured system risk report.

142|24|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Haaaiawd/Antigravity-Workflow-System --skill report-template
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-template
Source: https://github.com/Haaaiawd/Antigravity-Workflow-System/tree/main/.agent/skills/report-template
Command: npx skills add https://github.com/Haaaiawd/Antigravity-Workflow-System --skill report-template

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms raw analytical data from various scouting tools into a comprehensive, decision-ready system risk report, enabling architects to understand and address critical issues.

Core Features & Use Cases

  • Data Synthesis: Consolidates findings from build-inspector, runtime-inspector, git-forensics, and concept-modeler.
  • Structured Reporting: Generates a report adhering to a strict template, covering component inventory, dependencies, risks, and conceptual models.
  • Use Case: After running automated analysis tools on a codebase, use this Skill to compile all findings into a single report that clearly outlines technical debt, architectural risks, and missing components for the system architect.

Quick Start

Use the report-template skill to synthesize findings and generate a system risk report using the provided references/REPORT_TEMPLATE.md.

Frequently Asked Questions about report-template

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synthesize code analysis findings into a system risk report?

To synthesize code analysis findings into a system risk report, consolidate data from build-inspector, runtime-inspector, git-forensics, and concept-modeler into a structured template to identify technical debt and architectural risks.

What is the best way to consolidate technical debt and architectural risks for system architects?

The best way to consolidate technical debt and architectural risks is to cross-validate analytical findings from multiple codebase scouting tools into a single decision-ready report highlighting missing components and system risks.

How do I generate a structured report covering component inventory and dependencies?

Generate a structured report covering component inventory and dependencies by adhering to a predefined report template, cross-validating analytical findings to produce actionable intelligence for complexity guards.

Can I use this reporting approach without running build-inspector or runtime-inspector first?

No, this reporting approach requires analytical findings from build-inspector, runtime-inspector, git-forensics, and concept-modeler as input data to synthesize a comprehensive system risk report.

Does the generated system risk report need to follow a predefined report template?

Yes, the generated system risk report must strictly adhere to a predefined report template and save the output to a specific file path to ensure structured reporting for system architects.