report-generator

name	report-generator
version	1.0
description	Assembles upstream feasibility artifacts into a client-facing report in JSON and Markdown formats. This skill should be used when the pipeline has all or most of: analysis_packet.json, precedent_packet.json, constraints_packet.json, approval_pathway.json.
source	Assembled from pipeline outputs — no primary source authority
authority	N/A — synthesis skill
data_as_of	2026-03-07
pipeline_position	6
pipeline_inputs	normalized_data.json, analysis_packet.json, precedent_packet.json, constraints_packet.json, approval_pathway.json
pipeline_outputs	final_report.json, final_report.md
pipeline_upstream	all prior pipeline skills
pipeline_downstream	none — terminal skill

Report Generator

Purpose

Assemble a readable, auditable report from existing artifacts. Preserve uncertainty. Do not introduce new legal or planning conclusions that are not already supported upstream.

Use when

• analysis_packet.json exists
• The project needs a final report for human review or UI display
• Upstream artifacts are stable enough to cite

Do not use when

• Source discovery or extraction is still incomplete
• Major analysis questions are still unresolved
• The task is to do new research rather than present existing findings

Inputs

{
  "project_id": "uuid",
  "source_bundle_path": "source_bundle.json",
  "normalized_data_path": "normalized_data.json",
  "analysis_packet_path": "analysis_packet.json",
  "report_format": "json_and_markdown"
}

Optional supporting inputs:

• precedent_packet.json
• constraints_packet.json
• approval_pathway.json

If optional artifacts are missing, omit those sections cleanly rather than inventing placeholders.

Outputs

Produce:

• final_report.json
• final_report.md

Assembly Order

1. Establish the executive summary

Build this section only from the strongest supported upstream findings:

• verdict
• pathway signal
• overall confidence
• top opportunities and blockers

Never promote an inference into a fact in the summary.