Multi-Project Weekly Report Generator

Problem

Multiple people's weekly notes are scattered across personal tasks, making project-level summaries easy to misattribute, duplicate, or misclassify.
weekly-report-skill targets this workflow: given text that includes names and weekly work items, it extracts people and tasks, groups them by project keywords, and outputs a Markdown summary report. It is intended for turning fragmented records into a project-grouped weekly report, not for drafting emails or formal decks.

How It Works

• Input parsing: identify each person's name and corresponding tasks or outcomes.
• Project grouping: use keywords to infer projects, for example login or registration for the product frontend, API or backend for backend work, testing or regression for QA, deployment or server for DevOps, and SQL or migration for database work.
• Content consolidation: list owners and work items under each project; unclassified items go to Other.
• Output format: produce a Markdown report that can be pasted into docs, boards, or review notes.

Boundaries

The skill depends on the input containing enough names, task descriptions, and project keywords; if owners are missing, grouping may be less reliable. The keyword rules favor common engineering contexts, so new domain terms may need extra context. It does not create schedules, evaluate performance, or polish external copy; it focuses on aggregating multi-person content into a project-grouped Markdown weekly report.