What problem does it solve? Writing a professional red-team deliverable for an enterprise client is slow and error-prone: findings need consistent structure, calibrated severity, reproducible PoCs, and polished DOCX output. This Skill codifies the Subject / Observations / Description / Impact / Recommendation / PoC format so every finding ships client-ready. ## Core Features & Use Cases - Six-Section Finding Format: Enforces Subject, Observations, Description, Impact, Recommendation, and PoC per finding, with severity and status fields tuned for red-team engagements (including "patched mid-engagement"). - Full Document Structure: Provides the complete report skeleton — executive summary, risk summary table, findings, recon appendix, IoCs, and cleanup statement. - DOCX Generation Pipeline: Converts markdown to DOCX via pandoc with embedded screenshots, a reference style template, and image-count verification. - Use Case: After a one-week external red-team engagement with 14 confirmed findings, use this Skill to package them into a severity-ordered markdown report and render a branded DOCX with 16 embedded evidence screenshots for the client's CISO. ## Quick Start Use the redteam-report-template skill to package my confirmed engagement findings into a client-facing red-team report and generate the final DOCX with embedded screenshots.
