skills.rest
LucasMalessa
LucasMalessaCOMMUNITY
Explore all skills by this author →
GitHub

ring:delivery-status-tracking

Compare repository activity against a delivery roadmap to compute completion and variance.

Updated Mar 21, 2026
Search Tags:#analysis#roadmap#reporting#status#velocity#delivery#variance
One-click install
npx skills add https://github.com/LucasMalessa/TheRing --skill ring-delivery-status-tracking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ring:delivery-status-tracking
Source: https://github.com/LucasMalessa/TheRing/tree/main/pm-team/skills/delivery-status-tracking
Command: npx skills add https://github.com/LucasMalessa/TheRing --skill ring-delivery-status-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tracks delivery progress by comparing the actual repository activity against a defined roadmap to produce factual, evidence-based status reports for stakeholders.

Core Features & Use Cases

  • Grounded progress calculations using commits, PRs, branches, and releases to determine completion against the plan.
  • Variance analysis and risk insights, highlighting delays, bottlenecks, and critical path impact.
  • Automated status reports with traceable evidence links (GitHub commits, PRs, files) ready for stakeholder reviews.

Quick Start

Provide the roadmap and tasks files, then run the analysis to generate an evidence-based delivery report across all branches.

Frequently Asked Questions about ring:delivery-status-tracking

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

FAQPage Schema
How do I track delivery progress against a planned software roadmap?▼

Track delivery progress by comparing actual repository activity, such as commits and PRs, against a defined roadmap to compute completion and variance for factual status reporting.

How does variance analysis identify delays in a software delivery roadmap?▼

Variance analysis identifies delays by calculating the gap between planned roadmap milestones and actual repository activity, highlighting bottlenecks and critical path impact for stakeholder risk insights.

What do I need to generate an evidence-based delivery status report?▼

To generate an evidence-based delivery status report, you need a delivery roadmap file, a tasks file, and optionally a subtasks file, alongside repository access for analyzing commits, PRs, branches, and releases.

Can I automate stakeholder reporting using repository activity and a tasks file?▼

Yes, you can automate stakeholder reporting by analyzing repository commits, PRs, and releases against your tasks file to produce status reports with traceable evidence links.

What is the best way to compare planned roadmap milestones with actual repository activity?▼

The best way to compare planned milestones with actual activity is computing completion and variance using semantic analysis of commits, PRs, branches, and releases against your roadmap and current date.

Are there limitations to using roadmap variance analysis for progress tracking?▼

Limitations include requiring a pre-defined delivery roadmap and tasks file, and variance accuracy depends on consistent repository activity like commits and PRs reflecting actual development progress.

Related Skills

Explore More Product & Management Skills→
castrojocastrojo
2

roadmap

Create or update ROADMAP.md with milestones, timelines, and governance alignment for CNCF projects.

Community
Advanced
AgentTeam-TaichuAIAgentTeam-TaichuAI
630

pptx

Generate PowerPoint slide decks from structured data using Node.js and pptxgenjs.

Community
Advanced
bswrundquistbswrundquist

git-analyze

Analyze git repository history for activity, initiatives, bugs, and contributors.

Community
Advanced
Umbral-BotUmbral-Bot

linear-delivery-traceability

Verify Linear issue linkage, artifacts, and status for progress reports.

Official
Advanced