bee:delivery-status-tracking

Generates evidence-based delivery status reports by analyzing repository data against a roadmap.

2|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-delivery-status-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bee:delivery-status-tracking
Source: https://github.com/luanrodrigues/ia-frmwrk/tree/main/pm-team/skills/delivery-status-tracking
Command: npx skills add https://github.com/luanrodrigues/ia-frmwrk --skill bee-delivery-status-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures project status reports are grounded in concrete repository evidence, preventing false progress claims and uncovering blockers early.

Core Features & Use Cases

  • Evidence-Based Reporting: Generates status reports by analyzing commits, PRs, and branches against a delivery roadmap.
  • Variance Analysis: Compares planned vs. actual progress and dates to identify delays or early completions.
  • Insight Generation: Extracts trends in velocity, code activity, and quality indicators from repository data.
  • Use Case: Automatically generate a weekly progress report for stakeholders by analyzing the main development repository against the sprint's delivery roadmap, highlighting any tasks that are falling behind schedule with supporting evidence.

Quick Start

Use the bee:delivery-status-tracking skill to analyze the repository 'LerianStudio/my-project' and generate a status report.

Frequently Asked Questions about bee:delivery-status-tracking

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

FAQPage Schema
How do I generate evidence-based delivery status reports from repository activity?

To generate evidence-based delivery status reports, you can analyze repository activity like commits, PRs, and branches against a defined roadmap to calculate actual versus planned progress and identify delays.

What is the best way to track project progress against a sprint roadmap using git data?

Tracking project progress against a sprint roadmap involves scanning all repository branches, commits, and releases to perform semantic analysis of code content against task scopes, uncovering blockers early and preventing false progress claims.

Can I compare planned versus actual progress dates to identify development delays?

Yes, you can compare planned versus actual progress dates to perform variance analysis. This process identifies delays or early completions by matching development roadmap milestones against real repository commit and release activity.

How do I extract velocity and risk trends from repository commits and PRs?

Extracting velocity and risk trends from repository commits and PRs requires analyzing code activity and quality indicators. This generates insights into development speed and potential blockers by evaluating pull request data against task scopes.

Does project status tracking work without a pre-defined delivery roadmap?

No, project status tracking requires a defined delivery roadmap to function properly. The roadmap provides the planned progress baseline needed to compare against actual repository evidence and calculate accurate project variance.

What limitations exist when analyzing code content for sprint reporting?

A limitation of analyzing code content for sprint reporting is the requirement to scan all branches, commits, and releases. The semantic analysis depends entirely on repository data accuracy to prevent false progress claims and identify real blockers.