standup

Generate a three-line standup status from project logs and git history.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ronniepinnell/benchsight --skill standup-ronniepinnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standup
Source: https://github.com/ronniepinnell/benchsight/tree/main/.claude/skills/standup
Command: npx skills add https://github.com/ronniepinnell/benchsight --skill standup-ronniepinnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to generate a quick, consistent standup update without going through lengthy EA intake or meetings, by summarizing recent work, plans, and blockers.

Core Features & Use Cases

  • Automated extraction of recent work state from IMPLEMENTATION_PLAN.md and next_session.md.
  • Lightweight three-line status generation (Done, Next, Blockers) suitable for daily standups.
  • Works with local git logs and open issues labeled needs:user-input to surface blockers and activity.

Quick Start

Run the standup command to generate today's concise status report.

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 status from git logs and project files?

To generate a daily standup status, this Skill reads IMPLEMENTATION_PLAN.md, next_session.md, recent git logs, and open issues labeled needs:user-input to produce a three-line status covering done, next, and blockers.

How does an automated standup report read project blockers?

An automated standup report reads open issues labeled needs:user-input from your project repository to surface blockers, combining them with recent git activity and next_session.md to summarize current work state.

Can I use bash to automate agile standup updates for my software team?

Yes, you can use bash to automate agile standup updates. This Skill operates via a deterministic bash workflow that reads local project logs and files to output a concise three-line status for software team daily standups.

What's the best way to summarize recent work for a daily standup without meetings?

The best way to summarize recent work without meetings is using a bash workflow that extracts recent state from IMPLEMENTATION_PLAN.md and next_session.md, producing a lightweight done, next, and blockers status report.

Do I need specific project files to generate a three-line standup status?

Yes, you need IMPLEMENTATION_PLAN.md and next_session.md files in your project directory, along with accessible git logs and open issues labeled needs:user-input to generate the three-line standup status correctly.

What limitations exist when automating standup reports from project logs?

A limitation of automating standup reports is its reliance on specific files like IMPLEMENTATION_PLAN.md and next_session.md; without these files or git history and labeled issues, the bash workflow cannot produce a complete status.