Report Generator Lite

Problem: reports stall on structure and factual boundaries

When drafting daily reports, weekly updates, project reviews, performance summaries, or business analyses, teams often already have the raw material. The hard part is turning meeting notes, task lists, and work logs into readable text: conclusions are buried, status labels are mixed, risks are softened, and internal versus customer wording is not separated. This skill targets report drafting only. It does not create PPT, Word, PDF, or Excel files; it produces a clean, formal report body that can be pasted into other tools.

How it works: intent routing with factual discipline

Report Generator Lite routes by intent. Periodic reports use sections like overview, key items, risks, next steps, and support needed. Project reports use background, progress, outcomes, risks, and plans. Business analyses use conclusion, metrics, causes, and recommendations. Performance summaries use responsibilities, actions, results, capabilities, and follow-up plans. If the input is only “write my weekly report,” it outputs a fillable template or clearly labeled examples instead of inventing facts. Its key constraint is factual preservation: it avoids fabricating completion rates, amounts, rankings, acceptance conclusions, or awards; it does not rewrite “in progress” as “completed”; and it preserves stated risks and blockers. Before output, it checks headings, hierarchy, status distinctions, reader fit, and sensitive-data masking, which is useful for internal, leadership, customer, or redacted versions.