Agent skill
gsd-trace
Traces decisions and requirements through GSD artifacts. Use when user asks "why did we...", "what happened to...", or mentions decision history.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/gsd-trace
SKILL.md
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?