Tracing Knowledge Lineages

What problem does it solve?

Teams often repeat past failures or abandon effective solutions because they don't understand the historical context of decisions. This leads to wasted effort and suboptimal outcomes.

Core Features & Use Cases

• Decision Archaeology: Guides searching for past decisions in documentation, conversations, and Git history.
• Failed Attempt Analysis: Provides a framework to re-evaluate previously failed approaches in new contexts.
• Revival Detection: Helps identify "new" ideas that are actually old ones, allowing for lessons learned from previous incarnations.
• Paradigm Shift Mapping: Structures understanding of major architectural transitions, highlighting gains and losses.
• Use Case: Before proposing a new architectural change, you'd use this skill to understand why the current system was built, what alternatives were considered, and what lessons were learned from previous attempts.

Quick Start

1. Identify a current approach or "new" idea to investigate.
2. Use "Decision Archaeology" to search docs/decisions/, git log, or skills/collaboration/remembering-conversations.
3. Document findings: When adopted, why, what it replaced, and context.
4. If it's a "new" idea, search for historical precedents to detect revivals.