What problem does it solve? Turning technical evidence into a document that non-technical stakeholders can act on is hard: claims lose traceability, structure buries the decision, and rendered files ship with layout defects. This Skill provides a disciplined workflow for authoring executive briefs, proposals, and status reports where every material claim stays tied to its source. ## Core Features & Use Cases - Evidence Mapping: Builds a claim-to-source table separating fact, inference, recommendation, and unknowns before drafting begins. - Decision-Oriented Structure: Leads each section with conclusions, translates technical detail into impact, risk, and cost, and preserves trade-offs and dissenting evidence. - Rendered-Artifact QA: Inspects the actual DOCX/PDF output for page breaks, table width, chart labels, fonts, citations, and redaction completeness rather than trusting a successful file write. - Use Case: Convert a technical audit into a three-page Word brief for management, with sourced claims, labeled assumptions, and a verified rendered layout. ## Quick Start Ask the agent to turn your verified source material into an executive brief or client proposal in Word or PDF format, stating the audience, the decision needed, and the sources to cite.
