The Weekly Status Report That Writes Itself

Every Friday at 4pm, the same dread: "What did I even do this week?" Then 30 minutes of digging through Jira, Slack, and git logs to piece together a status update.

Never again.

The Automation

Here's what I set up (took 15 minutes):

1. A skill called /weekly-status
2. It reads: git log for the past 7 days, open tickets, completed tickets, and my notes
3. It outputs: a structured status report with accomplishments, in-progress, and next week priorities

Every Friday, I type /weekly-status and get a polished report in 30 seconds.

What It Produces

A clean report with sections:

• Completed: Features shipped, bugs fixed, PRs merged (pulled from git log)
• In Progress: Open branches, active tickets (pulled from git status + tickets)
• Blocked: Items waiting on others (pulled from notes and handoffs)
• Next Week: Planned priorities (pulled from backlog)

The Setup

The skill template is simple. It runs git commands, reads structured files, and formats the output. No external integrations needed — everything comes from your local project state.

Beyond Status Reports

The same pattern works for:

• Sprint retrospectives (what went well, what didn't)
• Release notes (changes since last tag)
• Standup updates (what did I do yesterday, what's today)

Any report that's derived from existing data can be automated. Stop spending time assembling information that already exists in your tools.

Check the daily practice guide for more automation patterns like this.