gsd-trace
Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.
npx skills add majiayu000/claude-skill-registry --skill gsd-trace --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# GSD Decision Archaeology Excavate GSD artifact timeline to reconstruct decision chains, requirement evolution, and phase rationale. ## Sources (authority order) 1. PROJECT.md Key Decisions 2. STATE.md Session Continuity 3. ROADMAP.md phase goals/criteria 4. Phase CONTEXT.md / RESEARCH.md 5. Plan SUMMARY.md outcomes 6. Git commit messages 7. Archived milestone docs ## Trace Process 1. **Identify query type** — decision rationale, requirement status, phase outcome, impact analysis 2. **Search sources** — start with highest authority, cross-reference downward 3. **Build timeline** — chronological events from artifacts 4. **Trace causality** — link decisions to requirements to implementation 5. **Answer directly** — cite specific sources and dates ## Query Types | Type | Primary Sources | |------|----------------| | Why decision X? | PROJECT.md Key Decisions, RESEARCH.md | | What happened to req Y? | REQUIREMENTS.md, STATE.md, milestones/ | | Phase N outcome? | ROADMAP.md, SUMMARY files, git commits | | What depends on X? | PLAN files, git history, code search | | What was tried/abandoned? | RESEARCH.md, STATE.md | ## Limitations Can only trace what GSD documented. Undocumented decis
- Sources (authority order)
- Trace Process
- Query Types
- Limitations
What does the gsd-trace skill do?
Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill gsd-trace --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.