gsd-stats
Provides a dashboard view of project progress and metadata.
Install
mkdir -p .claude/skills/gsd-stats && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12609" && unzip -o skill.zip -d .claude/skills/gsd-stats && rm skill.zipInstalls to .claude/skills/gsd-stats
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Display project statistics — phases, plans, requirements, git metrics, and timelineKey capabilities
- →Display phase progress.
- →Show plan execution metrics.
- →Report requirements completion.
- →Present git history statistics.
- →Visualize project timeline.
- →Map user questions to `request_user_input` for interactive prompts.
How it works
The skill aggregates and displays various project statistics by translating GSD workflow commands into Codex-compatible actions. It uses `request_user_input` for interactive prompts and `spawn_agent` for tasks.
Inputs & outputs
When to use gsd-stats
- →Checking project progress
- →Reviewing timeline status
- →Generating project metrics
About gsd-stats
Aggregates and displays key performance metrics and status reports for a project. It summarizes phases, plan statuses, and timeline information in a readable format.
Display project statistics — phases, plans, requirements, git metrics, and timeline
When not to use it
- →When `request_user_input` is rejected or unavailable, and the skill is not in TEXT_MODE.
- →When the user has not explicitly approved a specific default for a question.
- →When the workflow's documented contract does not state that defaults are safe.
Limitations
- →It cannot proceed without a user answer unless specific conditions are met.
- →It will not write workflow artifacts until the user has answered plain-text questions or conditions apply.
- →It requires schema detection to determine the available `spawn_agent` capabilities.
How it compares
This skill provides a consolidated view of project health and progress through automated reporting, offering a more efficient and consistent overview than manually gathering metrics from disparate sources.
Compared to similar skills
gsd-stats side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-stats (this skill) | 0 | 3mo | No flags | Beginner |
| task-master | 22 | 8mo | Review | Intermediate |
| agile-product-owner | 10 | 9mo | Review | Beginner |
| writing-plans | 15 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by AcidicSoil
View all by AcidicSoil →You might also like
task-master
sfc-gh-dflippo
AI-powered task management for structured, specification-driven development. Use this skill when you need to manage complex projects with PRDs, break down tasks into subtasks, track dependencies, and maintain organized development workflows across features and branches.
agile-product-owner
davila7
Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.
writing-plans
obra
Use when you have a spec or requirements for a multi-step task, before touching code
task-execution-engine
davila7
Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-design-assistant output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.
feature-design-assistant
davila7
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing architecture, or making significant changes to the codebase.
task-coordination-strategies
wshobson
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.