Gsd trace
Skill Tibsfox/gsd-skill-creator/project-claude/skills/gsd-trace
Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.From its SKILL.md
npx -y skills add Tibsfox/gsd-skill-creator --skill gsd-traceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
SKILL.md
1.5 KB, 294 tokens by cl100k_base, as published. Nobody here has run it
GSD Decision Archaeology
Excavate GSD artifact timeline to reconstruct decision chains, requirement evolution, and phase rationale.
Sources (authority order)
- PROJECT.md Key Decisions
- STATE.md Session Continuity
- ROADMAP.md phase goals/criteria
- Phase CONTEXT.md / RESEARCH.md
- Plan SUMMARY.md outcomes
- Git commit messages
- Archived milestone docs
Trace Process
- Identify query type — decision rationale, requirement status, phase outcome, impact analysis
- Search sources — start with highest authority, cross-reference downward
- Build timeline — chronological events from artifacts
- Trace causality — link decisions to requirements to implementation
- 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 decisions, verbal discussions, and vague commit messages are untraceable.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.