Report Engineering

Purpose

Reports fail when the writer optimizes for completeness rather than comprehension. A 20-page status report that nobody reads is worse than useless. This skill produces reports that match the audience's context: executives get the bottom line first, engineers get the data, and everyone gets clear next steps.

SOP: Report Generation

Step 1 - Audience and Report Type

Before writing, classify:

Audience:

• executive: Non-technical decision-maker. Needs impact and recommendations, not implementation details.
• technical: Engineer or tech lead. Needs specifics, data, and root cause.
• mixed: Product and engineering together. Lead with business impact, provide technical appendix.