Weekly Report Master: Daily Weekly and Monthly Report Generation

What It Solves

Engineers often keep work notes as scattered bullets, chat logs, git commit messages, and TODO lists. Submitting them directly can read like a log: highlights are buried, metrics are missing, and next-week plans are hard to verify. It may also miss the tone expected by different organizations.

How It Works

This skill turns fragmented material into a review-ready report. It first selects a style based on the user's role and organization: internet, public-sector, multinational, or promotion-review style, then structures the content by results, quantifiable impact, grouping, and follow-up plans.

• Quick mode: the user pastes raw notes and receives a Markdown report; on request it can produce .docx.
• Deep mode: for promotions, reviews, or mid-year summaries, it proposes 2–3 narrative angles before weakening off-topic details.
• Mid-year flow: it reviews H1 OKR/KPI completion, core business metrics, project delivery, efficiency gains, cross-team support, and growth, then ranks items by business impact and effort.

It avoids inventing numbers. Missing metrics are marked [please add data], issues must include mitigation ideas, and plans should be verifiable.

Boundaries

It is best for first drafts of daily, weekly, monthly, mid-year, and promotion reports. It does not confirm facts or automatically fill in missing numbers; the user must review and provide accurate data.