gsd-stats

Generate project statistics from phase progress, plan metrics, requirements, git history, and timeline signals.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-stats-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-stats
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-stats
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-stats-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams understand how a project is progressing by consolidating phases, plans, requirements, git activity, and timeline signals into one clear statistics view.

Core Features & Use Cases

  • Phase, plan, and requirement progress: Summarizes what is done versus what remains across planned deliverables.
  • Git and history metrics: Aggregates repository activity signals to support throughput and change analysis.
  • Project timeline overview: Produces a time-oriented snapshot to quickly spot delays, bottlenecks, and momentum.

Quick Start

Run the gsd-stats workflow at the repository root to generate a unified report of phases, plans, requirements, git metrics, and the project 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 requirement completion data?

To generate project statistics, run the gsd-stats workflow at your repository root. It aggregates requirement completion, git history stats, and timeline signals into a unified report for project health checks and delivery tracking.

What is the best way to consolidate phase progress and git metrics into a single project timeline?

Consolidating phase progress and git metrics requires reading local workflow data at a specified stats context path. This process produces an end-to-end, report-style snapshot to help spot delays, bottlenecks, and momentum.

Do I need external services to track engineering insights and plan execution metrics?

No external services are needed to track engineering insights and plan execution metrics. The Skill reads local workflow data and produces a report-style output with no external actions, ensuring your project statistics remain entirely local.

Can I use this approach for project health checks without external dependencies?

You can use this approach for project health checks without external dependencies. It requires no external components or dependencies, relying solely on local repository artifacts to produce a consolidated view of progress and repository activity.

What project artifacts are required to produce actionable metrics for engineering reviews?

Actionable metrics for engineering reviews require local workflow data containing phase progress, plan execution metrics, requirement completion records, and git history. These project artifacts are aggregated to provide a comprehensive view of repository activity.

When should I not use a consolidated statistics view for delivery tracking?

You should not use a consolidated statistics view for delivery tracking if your project lacks local workflow data or git history. The aggregation relies on existing phase progress and timeline signals to produce accurate project health checks.