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 red-team-specific status fields like "Confirmed; patched mid-engagement". - Full Document Structure: Provides the complete report skeleton — executive summary, engagement details, risk summary table, findings, recon appendix, IoCs, and cleanup statement. - DOCX Generation Pipeline: Includes a pandoc-based markdown-to-DOCX workflow with embedded screenshots, naming conventions, and image-count verification. - Use Case: After a one-week external red-team engagement, package 14 validated findings with 16 screenshots into a 52KB markdown report and a 2.2MB DOCX deliverable 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 with DOCX output.
