GSD Decision Archaeology
SkillDev toolsTraces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the GSD Decision Archaeology skill
What this skill tells your AI
The instructions your AI receives, as published by tibsfox/gsd-skill-creator in project-claude/skills/gsd-trace/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 69
- Forks
- 9
- Last commit
- Jul 2026
Advanced
- Catalog kind
- skill
- Gateway key
gsd-trace- Source
- github.com/tibsfox/gsd-skill-creator