gsd-trace

Name: gsd-trace
Availability: InStock
Author: Tibsfox

Traces the lineage of decisions and requirements across GSD artifacts.

69|9|Updated Jan 30, 2026

Search Tags:#decisions #requirements #artifacts #trace #history #archaeology #project-management

Ready to run

npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill gsd-trace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-trace
Source: https://github.com/Tibsfox/gsd-skill-creator/tree/main/examples/skills/gsd-trace
Command: npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill gsd-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill traces the history of decisions and requirements across GSD artifacts to provide context for future work.

Core Features & Use Cases

Decision chain reconstruction: reconstructs how a decision led to subsequent actions.
Requirement evolution tracking: shows how requirements changed over time with evidence.
Artifact timeline synthesis: builds a narrative linking commits, plans, and ROADMAP entries.
Evidence linking: connects decisions to specific artifacts for quick audit.

Quick Start

Reconstruct the decision history for the current project.

Frequently Asked Questions about gsd-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace the history of project decisions and requirements across markdown artifacts?▼

Trace the history of project decisions by reconstructing decision chains and requirement evolutions across PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and SUMMARY artifacts to provide structured evidence and commit references for past choices.

What is decision chain reconstruction in project management?▼

Decision chain reconstruction is the process of linking a past project decision to its subsequent actions and trade-offs by synthesizing timelines and commit references from existing project artifacts into a structured narrative.

How do I track how requirements evolved over time with evidence?▼

Track requirement evolution by analyzing REQUIREMENTS.md and ROADMAP.md histories to show how requirements changed over time, linking each modification to specific artifacts and commits for quick audit and verification.

Can I find where specific project trade-offs originated using markdown files?▼

Find where trade-offs originated by applying trace logic to PROJECT.md and SUMMARY artifacts, which connects past decisions to specific evidence and timelines, clarifying the context behind current project requirements.

What is the best way to build an artifact timeline for project archaeology?▼

Build an artifact timeline by synthesizing commits, plans, and ROADMAP entries into a narrative that links decisions to specific project artifacts, providing a structured history for quick audit and future context.