generate-burndown

Compute sprint burndown data and output JSON, CSV, or Markdown formats.

Updated Aug 27, 2026

Search Tags:#planning #metrics #agile #sprint #data-visualization #burndown

Ready to run

npx skills add https://github.com/gitwalter/cursor-agent-factory --skill generate-burndown

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-burndown
Source: https://github.com/gitwalter/cursor-agent-factory/tree/main/.cursor/skills/pm/generate-burndown
Command: npx skills add https://github.com/gitwalter/cursor-agent-factory --skill generate-burndown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates burndown chart data by querying sprint progress, calculating remaining work, and formatting data for visualization. It helps teams visualize sprint progress and identify if they're on track.

Core Features & Use Cases

Automated Burndown Generation: Compute burndown data from sprint items and dates.
Multi-format Output: Provide JSON, CSV, and Markdown table formats for charts.
Use Case: When planning or reviewing a sprint, generate a burndown to track progress and communicate status to stakeholders.

Quick Start

Use the generate-burndown skill to create burndown data for the current sprint from sprint data.

Frequently Asked Questions about generate-burndown

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

FAQPage Schema

How do I generate burndown chart data from sprint progress for agile tracking?▼

To generate burndown chart data, the Skill queries sprint progress to calculate remaining work and formats the output for visualization. It supports backend operations like getSprint or getBurndown to retrieve sprint items and dates.

What output formats can I use for sprint burndown data visualization?▼

Sprint burndown data can be output in JSON, CSV, or Markdown table formats for charts. These multi-format options allow integration with various data visualization tools and stakeholder reporting needs.

When do I need to compute burndown metrics during an agile sprint?▼

Compute burndown metrics during sprint planning, daily standups, and sprint reviews to track how work is moving toward completion. It helps teams visualize progress and identify if they are on track across current and past sprints.

Can I calculate remaining work for past sprints or only the current sprint?▼

You can calculate remaining work for both current and past sprints. The Skill applies backend operations like listItems if needed to retrieve historical sprint data, allowing you to compare progress across multiple iterations.

Does the burndown data generation provide insights for sprint planning and reviews?▼

Yes, the generated burndown data includes optional insights to help communicate sprint status to stakeholders. These insights assist in identifying whether the team is on track during sprint planning and reviews.

What is the best way to track remaining work for agile teams without manual calculation?▼

Automated burndown generation is the best way to track remaining work, as it queries sprint items and dates to compute burndown data automatically. This eliminates manual calculation errors during sprint planning and standups.