tracing-knowledge-lineages

Name: tracing-knowledge-lineages
Availability: InStock
Author: Sandgarden

Trace technical decision origins using Git history and decision records.

130|8|Updated Jan 23, 2026

Search Tags:#architecture #lineage #decision-archaeology #knowledge-tracing #historical-analysis #revival-detection

Ready to run

npx skills add https://github.com/sandgardenhq/sgai --skill tracing-knowledge-lineages-sandgardenhq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tracing-knowledge-lineages
Source: https://github.com/sandgardenhq/sgai/tree/main/cmd/sgai/skel/.sgai/skills/architecture/tracing-knowledge-lineages
Command: npx skills add https://github.com/sandgardenhq/sgai --skill tracing-knowledge-lineages-sandgardenhq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often forget why past architectural decisions were made, leading to repeated mistakes, unnecessary rewrites, or missed opportunities to revive proven ideas.

Core Features & Use Cases

Decision Archaeology: Locate and document the origins of current approaches using decision records, conversation logs, and Git history.
Failed Attempt Analysis: Re-examine prior failed attempts to determine if changed contexts make them viable again.
Revival Detection: Identify when “new” technologies are actually revivals of older practices and assess their suitability.
Paradigm Shift Mapping: Map major architectural transitions to capture lessons learned and preserve valuable knowledge.

Quick Start

Ask the skill to trace the lineage of the current caching implementation.

Frequently Asked Questions about tracing-knowledge-lineages

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

FAQPage Schema

How do I trace the history of architectural decisions in my codebase?▼

Trace the history of architectural decisions by analyzing decision records, conversation archives, and Git history to generate structured lineage documentation that explains why current approaches exist.

Why does our team keep repeating past technical mistakes?▼

Teams repeat past technical mistakes when historical knowledge of architectural decisions is lost, making it difficult to evaluate new ideas or understand why existing solutions were originally chosen.

What is the best way to analyze failed technical attempts and check if they are viable again?▼

Analyze failed technical attempts through failed attempt analysis and revival detection, re-examining prior approaches against changed contexts to determine if older practices are viable again.

Can I map major architectural transitions to preserve lessons learned from paradigm shifts?▼

Map major architectural transitions using paradigm shift mapping to capture lessons learned and preserve valuable knowledge about historical technical decisions and their evolution.

Does decision archaeology work without dedicated architecture decision records?▼

Decision archaeology works without dedicated architecture decision records by leveraging conversation archives and Git history to reconstruct the origins and evolution of technical approaches.