tracing-knowledge-lineages

Traces the historical evolution of ideas and decisions within a project.

2|Updated Jan 27, 2026

Search Tags:#architecture #decision making #knowledge management #technical debt #history #lessons learned

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you understand the history and evolution of ideas, approaches, and decisions within a project or organization, preventing the repetition of past failures and rediscovering forgotten solutions.

Core Features & Use Cases

Decision Archaeology: Uncover the reasons behind current approaches by examining decision records, conversations, and Git history.
Failed Attempt Analysis: Understand why previous attempts at a solution failed by analyzing the context, specific failure modes, and changes in circumstances.
Revival Detection: Identify if a "new" idea is a revival of a past approach and assess if the context has changed sufficiently for it to succeed now.
Use Case: Before proposing a major architectural change, use this Skill to trace the lineage of the current architecture, understand why it was chosen, and identify any past attempts at similar changes and their outcomes.

Quick Start

Trace the lineage of the current caching strategy by searching git history for relevant decision records.

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 project?▼

Trace architectural decisions by performing decision archaeology, which examines decision records, conversations, and Git history to uncover the original context and reasons behind current methods. This prevents repeating past design failures.

Why do past attempts at solving technical debt fail when revisited?▼

Past attempts at solving technical debt fail due to specific historical context and failure modes. Failed attempt analysis evaluates these previous errors and checks if circumstances have changed enough to ensure a current solution succeeds.

How can I tell if a new software architecture idea is a revival of a past approach?▼

Detect if a new software architecture idea is a revival by tracing the lineage of previous concepts. Revival detection identifies past approaches and assesses whether the project context has shifted sufficiently to support the idea today.

What is decision archaeology and when do I need it for knowledge management?▼

Decision archaeology is the process of excavating historical project decisions and approaches from records and Git history. You need it when justifying current methods or evaluating recurring concepts to inform current problem-solving and innovation.

How do I analyze why a previous technical approach failed before proposing a major change?▼

Analyze previous technical failures by tracing the historical evolution of ideas within the project. Examine past decision records and failed attempt analysis to understand specific failure modes before proposing major architectural changes.

What are the limitations of using Git history for tracing knowledge lineages?▼

Tracing knowledge lineages relies on the availability of historical artifacts like decision records and Git history. Its limitation is the potential lack of documented context or conversations surrounding past approaches, requiring deeper archaeological excavation.