Generate structured technical reports with templates and evidence-first sections. Use when users request architecture reviews, post-mortems, debug investigations, or research summaries with standardized report output.
Produce technical reports with consistent structure and verifiable evidence.
python3 scripts/report_gen.py --type <arch-review|post-mortem|research-summary|debug-investigation> --title "<title>" [--scan <dir>] [--output <file>]
arch-review: system design, trade-offs, integration points, risk analysis.post-mortem: incident timeline, root cause, impact, action items.debug-investigation: bug diagnosis and resolution with before/after validation.research-summary: findings synthesis, methodology, confidence, and recommendations.MEDIUM is the right setting because structure is fixed by templates while content and evidence stay user-driven.Use one command to generate the required report type.
python3 scripts/report_gen.py --type arch-review --title "Gateway Architecture Review"
python3 scripts/report_gen.py --type post-mortem --title "Database Outage 2026-02-14"
python3 scripts/report_gen.py --type research-summary --title "Skill Trigger Precision Analysis"
python3 scripts/report_gen.py --type debug-investigation --title "OAuth Token Refresh Failure"
Control output location and enrich draft context from local files.
python3 scripts/report_gen.py \
--type debug-investigation \
--title "OpenAPI Parser Crash" \
--author "Archie" \
--scan ./dev/openapi-integrator \
--keywords traceback parser schema \
--max-files 30 \
--output ./research/2026-02-14/DBG-openapi-parser-crash.md
Template customization rules:
assets/templates/ unchanged.--output for date-stamped or queue-specific report destinations.Enforce evidence-first writing and stronger review bars.
references/guides/evidence-first-reporting.md and assets/evidence-section-guide.md as pre-review checks.Recommended --scan enrichment patterns:
--scan . --keywords error exception timeout failed--scan ./research --keywords metric benchmark latency--scan ./dev/<project> --keywords stack trace root cause fixAll templates live in assets/templates/ and are selected via --type.
assets/templates/references/examples/references/guides/