Tracing Knowledge Lineages

What problem does it solve?

Teams often repeat past mistakes, abandon viable solutions prematurely, or reinvent "new" ideas without understanding their historical context. This leads to wasted effort and suboptimal decisions. This skill provides a structured approach to understanding the evolution of ideas and decisions.

Core Features & Use Cases

• Decision Archaeology: Guides searching decision records, conversations, and Git history to understand "why X was chosen."
• Failed Attempt Analysis: Provides a framework to re-evaluate past failures, considering changed contexts and preventing premature dismissal of solutions.
• Revival Detection: Helps identify if "new" ideas are actually old ones, and what lessons can be learned from their previous incarnations.
• Use Case: Before proposing to replace an existing system, trace its lineage to understand the original problems it solved and why previous alternatives were rejected, ensuring your new proposal addresses historical challenges.

Quick Start

Before proposing a new approach, trace its lineage:

1. Check decision records (e.g., docs/decisions/, docs/adr/)
2. Search conversations (using Remembering Conversations skill)
3. Git archaeology (e.g., git log --all --full-history -- path/to/file)
4. Ask the original author (if available)