skills.rest
ev3rlit
ev3rlitCOMMUNITY
Explore all skills by this author →
GitHub

gsd-stats

Aggregate project statistics from phases, plans, requirements, and git history.

Updated Apr 2, 2026
Search Tags:#statistics#data-analytics#sprints#project-management#progress-tracking#git-metrics
One-click install
npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-stats-ev3rlit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-stats
Source: https://github.com/ev3rlit/magam-canonical-archive/tree/main/.codex/skills/gsd-stats
Command: npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-stats-ev3rlit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates and presents key project metrics to reveal progress, gaps, and trends across phases, plans, requirements, and git history.

Core Features & Use Cases

  • Phase progress tracking across milestones
  • Plan execution metrics, backlog vs. completion, and burn-down insights
  • Requirements visibility with traceability to commits and issues
  • Timeline visualization combining schedules, sprints, and release dates
  • Use Case: A PM reviews sprint health by comparing planned vs actuals and quickly identifies blockers to re-prioritize work.

Quick Start

Run the stats workflow to aggregate phase progress, plans, requirements, git metrics, and timeline for your current project.

Frequently Asked Questions about gsd-stats

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

FAQPage Schema
How do I track project progress across multiple sprints and milestones?▼

Project progress tracking aggregates data from repositories and issue trackers to present a unified view of phase progress, plan execution, requirements, git history, and timeline across multiple sprints and milestones.

Can I visualize sprint health by comparing planned vs actual metrics?▼

Sprint health visualization compares planned versus actual metrics, surfacing backlog completion rates and burn-down insights so project managers can identify blockers and re-prioritize work effectively.

What is the best way to aggregate git history and issue tracker data for progress tracking?▼

Aggregating git history and issue tracker data produces a unified dashboard combining schedules, sprints, and release dates to satisfy data collection, aggregation, and visualization requirements for historical analysis.

Does this approach provide requirements traceability to git commits and issues?▼

Requirements traceability links tracked requirements directly to relevant git commits and issues, providing visibility into how specific code changes map to defined project requirements.

Can I use these project statistics dashboards for software projects with complex release timelines?▼

These project statistics dashboards apply to software projects with multiple sprints and milestones, combining schedules, sprints, and release dates into a comprehensive timeline visualization for historical analysis.

What limitations exist when tracking phase progress across non-software project plans?▼

Tracking phase progress is optimized for software projects with multiple sprints, milestones, git history, and issue trackers; non-software projects lacking these structured development artifacts may not yield comprehensive statistics.

Related Skills

Explore More Data & Analytics Skills→
SeongHuniSeongHuni

changelog

Generate changelogs from Git history, sprint data, and design documents.

Community
Intermediate
giovannimnzgiovannimnz

gsd-progress

Scan phase data and generate a structured project progress report.

Community
Intermediate
TruCol270TruCol270
1

gsd-stats

Aggregate project data to compute phase, plan, requirements, and git metrics.

Community
Intermediate
amo-tech-aiamo-tech-ai
2

linear-sprint

Automates sprint planning and analytics tasks via a task management tool's interface.

Community
Intermediate