gsd-stats
Provides project reporting and status statistics.
Install
mkdir -p .claude/skills/gsd-stats-satish627 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12611" && unzip -o skill.zip -d .claude/skills/gsd-stats-satish627 && rm skill.zipInstalls to .claude/skills/gsd-stats-satish627
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
- →Illustrate project timeline
How it works
The skill is invoked by mentioning $gsd-stats, processes user arguments, and executes a stats workflow to display project statistics.
Inputs & outputs
When to use gsd-stats
- →Reporting project status
- →Reviewing requirement progress
- →Checking git metrics
About this skill
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-stats. - Treat all user text after
$gsd-statsas{{GSD_ARGS}}. - If no arguments are present, treat
{{GSD_ARGS}}as empty.
B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
Multi-select workaround:
- Codex has no
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.
Execute mode fallback:
- When
request_user_inputis rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.
C. Task() → spawn_agent Mapping
GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y")→spawn_agent(agent_type="X", message="Y")Task(model="...")→ omit (Codex uses per-role config, not inline model selection)fork_context: falseby default — GSD agents load their own context via<files_to_read>blocks
Parallel fan-out:
- Spawn multiple agents → collect agent IDs →
wait(ids)for all to complete
Result parsing:
- Look for structured markers in agent output:
CHECKPOINT,PLAN COMPLETE,SUMMARY, etc. close_agent(id)after collecting results from each agent </codex_skill_adapter>
<execution_context> @/Users/satish/Desktop/AI-Powered Learning Assistant/.codex/get-shit-done/workflows/stats.md </execution_context>
<process> Execute the stats workflow from @/Users/satish/Desktop/AI-Powered Learning Assistant/.codex/get-shit-done/workflows/stats.md end-to-end. </process>When not to use it
- →When only codebase structure assessment is needed
- →When detailed code mapping is required
Limitations
- →Focuses on displaying project statistics as defined by the workflow
- →Relies on the execution of the stats workflow
How it compares
This skill focuses on displaying complete project statistics, unlike other tools that might only provide codebase structure or mapping.
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 | 4mo | No flags | Beginner |
| gsd-stats | 0 | 1mo | No flags | Beginner |
| cto-engineering-metrics | 5 | 9mo | No flags | Advanced |
| summarize-activity | 6 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Satish627
View all by Satish627 →You might also like
gsd-stats
AcidicSoil
Display project statistics — phases, plans, requirements, git metrics, and timeline
cto-engineering-metrics
rinaldofesta
Expert methodology for defining, tracking, and interpreting engineering performance metrics including DORA, team health, productivity, and executive reporting.
summarize-activity
alpinejs
Summarize recent GitHub activity — discussions, PRs, issues, events, traffic — into an actionable report so you can stay on top of the project without reading everything.
conductor-status
sickn33
Display project status, active tracks, and next actions
status
serithemage
Shows project progress, phase completion status, test coverage, and deployment info. Use when checking what has been implemented, what remains, or current operational state.
daily-report
ianphil
Generates a comprehensive daily report covering ADO work items, Teams chats, calendar, email, local mind next-actions, and inbox notes. Run this each morning to get a scannable summary of everything you need to know to start your day. Use when user asks for "daily report", "morning briefing", or "wh