weekly-report

To write a weekly work summary, narrate your tasks and outcomes to guide modular collection, categorize work by modules, and surface impact to produce a structured Markdown document. This approach ensures completeness by capturing background, actions, results, and next steps.

Yes, you can generate a status update report in Markdown for cross-team sharing. The skill provides a consistent template-driven structure that captures background, actions, and results, outputting a ready-to-submit document suitable for long-term archiving and cross-team alignment.

This weekly report template works for product, technical, and operations roles. It adapts its flexible categorization to different role contexts, guiding users to collect material and structure their narrative by capturing specific background, actions, results, and upcoming next steps.

The best way to structure a progress-tracking report is to categorize weekly activities into modular blocks that capture background, actions, and results, while explicitly detailing upcoming next steps. This value-focused structure ensures clear communication of progress and future planning.

To ensure your weekly report captures impact and next steps clearly, use a guided template to narrate work in modular blocks. This structure surfaces the value of actions and records changes for the next iteration, producing a complete and shareable summary.

A limitation for data collection and narrative structuring is that the skill requires users to manually narrate their weekly tasks and outcomes. It relies on user-provided descriptions to categorize modules and does not automatically pull activity data from external tracking platforms.