gsd-stats

Aggregate phase progress, plan execution, requirement completion, and git history into project statistics.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-stats-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-stats
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-stats
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-stats-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams quickly understand how a project is progressing by turning scattered information (phases, plans, requirements, and git history) into a single, readable statistics view.

Core Features & Use Cases

  • Phase and plan progress: Summarizes what has been completed across phases and how plans are executing.
  • Requirement completion tracking: Highlights progress toward requirements so gaps are visible.
  • Git metrics and timeline: Uses repository history to provide commit/activity context and an overall timeline.
  • Use case: After a sprint, you want stakeholders to see what was accomplished, which requirements are still incomplete, and how development activity unfolded over time.

Quick Start

Use the gsd-stats skill to run the project statistics workflow end-to-end for phases, plans, requirements, git metrics, and timeline.

Frequently Asked Questions about gsd-stats

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

FAQPage Schema
How do I generate project statistics from git history and tracked phases?

You generate project statistics by executing the designated stats workflow, which aggregates phase progress, plan execution metrics, and requirement completion status alongside git history timeline data. This workflow computes and presents the requested metrics in a single readable view.

What is the best way to track requirement completion and git activity together?

The best way to track requirement completion with git activity is by aggregating repository commit history and phase plan execution data. This approach highlights progress toward requirements so gaps are visible alongside the development timeline.

Can I use project phase progress data for post-sprint reporting?

Yes, you can use phase progress data for post-sprint reporting by summarizing completed phases and plan execution metrics. This provides stakeholders with a view of what was accomplished and which requirements remain incomplete after a sprint.

How does git commit timeline aggregation work for project health checks?

Git commit timeline aggregation works by using repository history to provide commit and activity context for ongoing project health checks. It combines this git timeline data with phase progress and requirement tracking to compute comprehensive project statistics.

Do I need any external dependencies to compute git metrics and phase progress?

No external dependencies are required to compute git metrics and phase progress. The statistics generation runs end-to-end as defined in its linked workflow file, relying solely on your existing repository phases, plans, requirements, and git history.