running-standup

Analyze active sprint tasks to classify statuses and detect stalls.

3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kazukinagata/waggle --skill running-standup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: running-standup
Source: https://github.com/kazukinagata/waggle/tree/main/skills/running-standup
Command: npx skills add https://github.com/kazukinagata/waggle --skill running-standup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates sprint status reporting by analyzing tasks in the active sprint, detecting stalls, and highlighting blockers, reducing manual standup overhead.

Core Features & Use Cases

  • Automated standup reports: summarize active sprint progress with running, stalled, and blocked tasks.
  • Stall detection & analytics: computes elapsed time since dispatch and flags potential delays.
  • Cross-team visibility: supports multiple teams and backlogs to present a consolidated view.

Quick Start

Ask Waggle to generate the current sprint standup report with stall detection.

Frequently Asked Questions about running-standup

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

FAQPage Schema
How do I automate sprint standup reports with stall detection?

To automate sprint standup reports, this skill analyzes active sprint tasks to detect stalls and blockers. It fetches sprint data, computes stall thresholds, and classifies tasks as RUNNING, COMPLETED, STALLED, or BLOCKED with elapsed times to reduce manual reporting overhead.

What is stall detection in agile sprint monitoring?

Stall detection in agile sprint monitoring computes elapsed time since task dispatch to flag potential delays. It identifies tasks that are no longer progressing, highlighting blockers and stalled items before they impact the sprint goal.

How does automated standup reporting work across multiple teams and backlogs?

Automated standup reporting consolidates active sprint tasks across multiple teams and backlogs by fetching data via the headless provider. It analyzes progress and presents a consolidated view of running, stalled, and blocked items.

Do I need a headless provider to generate sprint status reports?

Yes, generating sprint status reports requires access to the headless provider to fetch the active sprint and tasks, compute stall thresholds, and render the structured standup report.

Can I track blocked and stalled kanban tasks automatically?

Yes, you can automatically track blocked and stalled kanban tasks. The skill analyzes active sprint tasks, applies stall thresholds, and flags items as STALLED or BLOCKED, providing elapsed times and summaries for quick visibility.

What are the limitations of automated sprint stall detection?

Automated sprint stall detection is limited to analyzing tasks within the active sprint and requires headless provider access. Its stall detection relies on computing elapsed time since dispatch rather than evaluating task complexity or external dependencies.