Agent Skills: week-report

Prepare weekly management report. Use when asked to create a weekly report,

UncategorizedID: mir/maratai/week-report

Install this agent skill to your local

pnpm dlx add-skill https://github.com/mir/maratai/tree/HEAD/claude-maratai-manager/skills/week-report

Skill Files

Browse the full folder contents for week-report.

Download Skill

Loading file tree…

claude-maratai-manager/skills/week-report/SKILL.md

Skill Metadata

Name
week-report
Description
"Prepare weekly management report. Use when asked to create a weekly report, summarize recent changes, or prepare a demo of what was done in the past week."

You are the project manager. You need to prepare a report and a small demo of what was done past several days.

Do the following steps in separate tasks:

  1. Inspect what was changed in the repo for the past 7 days from the user perspective.
  2. Inspect code diffs for each change, not only the commit messages.
  3. Query the database for explicit demo data without placehoders like "X" or any, only existing recent data that is important, usefull in practical scenarious.
  4. Group the changes that are related to each other
    1. If the subsequent changes are improvements of the previous ones
    2. If subsequent changes are built on top of the previous ones
    3. If changes solve the same underlying users problem
    4. Logically relate to the same problem
  5. Create a report in the following format:
  • Leading emoji and short sentence describing the change (group of changes) from the end user perspective.
    • Create an explicit, step-by-step demo scenario using real data from the database (step 3). Each demo must include:
      • Numbered steps with exact text to type, buttons to click, or pages to navigate to
      • Real values
      • Mention real users by first name who already used the feature (e.g., "Ryan asked about enterprise ACV using this")
    • If it is a technical change, refactor, bugfix, or internal change - skip the demo scenario (continue) If the changes group is visible to the end user, mark it with a heart emoji. If it is a refactor, bug fix, or technical improvement - mark with corresponding emoji.
  1. Group the internal improvements, refactoring, documentation, todo changes testing in a single line.