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, business-translated impact, reproducible PoCs, and polished DOCX output. This Skill codifies the complete 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 red-team-specific status fields like "Confirmed; patched mid-engagement". - Full document structure: Provides the executive summary, risk summary table, recon appendix, IoC section, and cleanup statement expected in enterprise deliverables. - DOCX pipeline: Converts markdown reports 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 validated findings, use this Skill to package them into a severity-ordered markdown report with embedded screenshots, then render a styled DOCX for the client's CISO. ## Quick Start Use the redteam-report-template skill to package my validated engagement findings into a client-facing red-team report and export it as DOCX.
