standup-formatter

ChaiWithJai's avatarfrom ChaiWithJai

Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 23, 2025
[Meeting Productivity]

When & Why to Use This Skill

The Standup Formatter skill is designed to streamline team communication by transforming raw work activity into professional, high-impact standup reports. By adhering to agile principles, it helps users move away from activity-logging and toward outcome-based reporting, focusing on what truly matters: progress, future focus, and actionable blockers. This tool ensures that daily updates are concise, readable, and effective for both synchronous and asynchronous team environments.

Use Cases

  • Individual Daily Updates: Automatically convert your daily tasks and Git activity into a structured 'Done, Today, Blockers' format for Slack or Microsoft Teams, ensuring your contributions are visible and clear.
  • Team Status Aggregation: Consolidate updates from multiple team members into a unified report to provide project managers and stakeholders with a high-level overview of team velocity and health.
  • Project-Specific Reporting: Generate focused status summaries for specific projects by filtering source data like calendar events and manual inputs to keep stakeholders informed on key milestones.
  • Blocker Resolution: Use the structured 'Blockers' section to clearly articulate dependencies and obstacles, making it easier for team leads to provide the necessary support and keep the project on track.
namestandup-formatter
descriptionUse when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.
## Standup Philosophy

Purpose

Standups exist to:

  1. Share blockers that need help
  2. Coordinate on dependencies
  3. Keep work visible

Standups do NOT exist to:

  • Report hours worked
  • Justify existence
  • Detail every task

The Ideal Standup

Done: What you completed (outcomes, not activities) Today: What you're working on (1-2 focus items) Blockers: What's preventing progress (specific, actionable)

Time Budgets

  • Speaking: 60 seconds max per person
  • Written: 3-5 bullet points total
  • Detail level: Enough to understand, not to replicate

Format Guidelines

Good Examples

Done: Merged PR for user auth (#234)
Today: Starting payment integration
Blockers: Waiting on API spec from backend team

Bad Examples

Done: Worked on stuff, had meetings, reviewed some code,
      wrote tests, fixed bugs, updated docs, etc.
Today: More of the same
Blockers: Nothing

Async vs Sync

Async (written):

  • More detail acceptable
  • Include links to PRs/tickets
  • Post by 9am team time

Sync (spoken):

  • Extremely concise
  • No reading from notes
  • Save details for follow-ups
What standup format do you need?
  1. Individual - Your personal standup
  2. Team - Aggregate team status
  3. Project - Status for specific project

For what timeframe?

  • Yesterday/today (daily)
  • This week (weekly)
  • Custom dates

Source data?

  • Git activity
  • Calendar events
  • Manual input
## Individual Standup 
## Standup - [Date]

### Done
- [Completed item 1]
- [Completed item 2]

### Today
- [Focus item 1]
- [Focus item 2]

### Blockers
- [Blocker with specific need] / None

Team Standup

## Team Standup - [Date]

### [Person 1]
- Done: [summary]
- Today: [focus]
- Blockers: [if any]

### [Person 2]
...