standup

Aggregate recent activity from connected tools into a Yesterday/Today/Blockers report.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill standup-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/engineering-standup
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill standup-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standups often require gathering updates from multiple tools; this skill automates that, turning scattered activity into a concise daily report.

Core Features & Use Cases

  • Automated Standups: Collate yesterday's work across source control, project trackers, and CI/CD into a concise update.
  • Configurable Formats: Produce sections for Yesterday, Today, and Blockers; format for Slack, email, or your team's tool.
  • Use Case: A developer finishing a sprint can generate a quick daily standup to share with the team.

Quick Start

Ask me to generate today's standup by summarizing yesterday's activity across connected tools.

Frequently Asked Questions about standup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a daily standup from recent project activity across multiple tools?

Generate a daily standup by automatically aggregating recent activity from connected source control, issue trackers, and CI/CD tools into a concise Yesterday/Today/Blockers report.

What is the best way to format automated standup updates for Slack or email?

The best way to format automated standup updates is by applying optional customization to present aggregated activity into structured sections built specifically for Slack, email, or your team's preferred tool.

Can I collate yesterday's work from source control and CI/CD pipelines into a single report?

Yes, you can collate yesterday's work from source control and CI/CD pipelines by aggregating activity across connected tools into a single, concise daily status update for your software team.

Does this approach to daily standups require manual input for sprint tracking?

No, automated daily standups do not require manual input for sprint tracking, as the process pulls and formats recent activity directly from your connected project trackers and source control tools.

When should I use an automated standup update instead of writing a manual daily report?

Use an automated standup update when your team needs quick status updates across scattered source control, issue trackers, and CI/CD activity, replacing the manual effort of gathering updates from multiple tools.