Verified:GitHub

project-burnup

Generates Jira burn-up charts by cross-referencing Jira tickets, git branches, and GitLab merge requests.

Updated Jul 22, 2026

Search Tags:#mcp #project tracking #jira #gitlab #merge requests #progress reporting #burn-up chart

One-click install

npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill project-burnup-trigent-software-pvt-ltd

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: project-burnup
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/product/skills/project-burnup
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill project-burnup-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually tracking project progress across Jira tickets, git branches, and GitLab merge requests is error-prone and time-consuming. This Skill automates burn-up chart generation by reconciling all three data sources into a single JSON data file and HTML chart. ## Core Features & Use Cases - Multi-source progress tracking: Queries Jira Units and Bolts via the Atlassian MCP server, checks git branches and merge commits, and pulls GitLab MR timestamps to resolve true work status. - Discrepancy detection: Flags cases where Jira status disagrees with git reality, such as tickets marked Done with no merge commit on main. - Interactive onboarding: Auto-discovers Units and Bolts from Jira on first run and writes a reusable docs/burnup-config.yml configuration file. - Use Case: A delivery lead runs the skill from a project root each week to refresh the burn-up chart, resolve TBD bolt mappings, and surface Jira-versus-git discrepancies before a status review meeting. ## Quick Start Run the project-burnup skill from the root of my project to update the burn-up chart using the config in docs/burnup-config.yml.

Frequently Asked Questions about project-burnup

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

FAQPage Schema

How do I generate a burn-up chart from Jira tickets?▼

Run the skill from the root of your target project. It reads docs/burnup-config.yml, queries Jira Units and Bolts through the Atlassian MCP server, cross-references git and GitLab MR data, and writes a burnup JSON file plus an HTML chart.

How do I track Jira ticket status against GitLab merge requests?▼

The skill searches GitLab MRs by source branch name and bolt ID across the primary repo and any additional repos. It resolves merged, on-branch, or in-progress status from git evidence, which overrides the Jira status when they disagree.

What prerequisites are needed to run a Jira burn-up chart update?▼

You need the Atlassian MCP server connected and the glab CLI authenticated via glab auth login. The skill verifies both on startup and stops with a clear message if either check fails.

What happens if the burnup config file is missing?▼

The skill runs an interactive onboarding flow that asks for project identity, Jira instance URL, and git project keys, then auto-discovers Units and Bolts from Jira and writes a populated docs/burnup-config.yml.

Why does my Jira ticket show Done but the burn-up chart shows it incomplete?▼

This is a jira-ahead discrepancy: Jira says Done but no merge commit exists on main. Git reality overrides Jira status, so the bolt is not counted as merged until the merge commit is found.

Can the burn-up chart track bugs alongside planned work?▼

Yes. The skill queries Jira bugs that are children of any Unit, links them to related bolts via issue links, and searches GitLab MRs by bug key to determine their git status and MR timestamps.