gsd-stats

Compute phase progress, plan execution, requirement completion, git history, and timeline statistics.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-stats-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-stats
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-stats
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-stats-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to quickly understand where a project stands—what’s completed by phase and plan, which requirements are done, and how git activity and timelines are trending—without manually assembling status from scattered sources.

Core Features & Use Cases

  • Phase, plan, and requirement visibility: Surfaces progress across phases, plan execution, and requirement completion.
  • Git history and metrics: Provides git-related statistics to contextualize momentum and change patterns.
  • Timeline reporting: Summarizes the project timeline so stakeholders can see delivery cadence and sequencing.

Quick Start

Use the gsd-stats skill to generate comprehensive project statistics from the workflow context at $HOME/.claude/get-shit-done/workflows/stats.md.

Frequently Asked Questions about gsd-stats

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

FAQPage Schema
How do I generate a project status report with phase progress and git metrics?

Generate project status reports by computing phase progress, plan execution, requirement completion, git history stats, and timeline from workflow context. It produces a consolidated statistics display for stakeholder visibility without manual assembly from scattered sources.

What is the best way to track requirement completion and plan execution metrics together?

Track requirement completion and plan execution by summarizing project statistics across multiple dimensions. It surfaces progress for phases, plans, and requirements in a single comprehensive view, eliminating the need to manually correlate data from different tracking systems.

Can I use this to visualize git history statistics alongside project timeline data?

Git history statistics and project timeline data are visualized together in a consolidated dashboard. It contextualizes momentum and change patterns by computing git-related metrics alongside delivery cadence and sequencing for a comprehensive progress overview.

Do I need a specific workflow context file to report project statistics?

A specific workflow context file is required to report project statistics. It reads workflow context from the stats.md path to produce the end-to-end statistics display, ensuring accurate phase tracking and progress reporting based on predefined project data.

How does progress dashboard reporting handle scattered project status data?

Progress dashboard reporting consolidates scattered project status data by computing statistics across phases, plans, requirements, and git history. It provides stakeholders a single comprehensive view of progress and activity, solving the problem of manually assembling status updates.

What limitations exist when tracking project timeline and phase progress from workflow context?

Tracking project timeline and phase progress depends entirely on reading workflow context from the specified stats.md path. Statistics generation requires this file to be present and properly maintained, as no external data sources are integrated for consolidated reporting.