weekly-report

Automate weekly report generation by summarizing project activity from commit history and experiment records into a concise communication brief and an IMRaD-formatted technical report for stakeholders. The skill targets audiences from executives to team leads.

An IMRaD format report structures technical project updates into Introduction, Methods, Results, and Discussion sections. You need it when presenting detailed, executive-equivalent updates to stakeholders who require formal documentation of project activity.

Generate a non-technical executive summary by consolidating project documents and commit history into bullet-point updates suitable for non-technical audiences. The skill uses the project charter as context to frame the communication brief.

Yes, you can use commit history and experiment records to create a project charter-based report. The skill collects data from these sources and uses the project charter as context to generate both a team-friendly summary and a technical report.

Format weekly project reports by writing outputs to _docs/weekly-report/{YYYYMMDD}.md and related artifacts. The skill automatically structures the generated communication summary and IMRaD-style report into this defined document location.

The best way to consolidate project activity for team leads and executives is generating dual outputs: a bullet-point communication brief for non-technical stakeholders and a formal IMRaD-style technical report for detailed review, both derived from commit history and experiment records.