tracing-knowledge-lineages_skill

Overview

This skill helps you trace the history of ideas, decisions, and architecture to rediscover old solutions, avoid repeating past failures, and make informed changes. It teaches practical techniques to map when and why approaches were adopted, what failed before, and whether revival makes sense. Use it to ground proposals in documented context rather than fashion or intuition.

How this skill works

The skill inspects decision records, git history, issue and PR discussions, and conversation archives to build a lineage for current approaches. It provides structured templates (decision archaeology, failed-attempt analysis, revival detection, paradigm-shift mapping) so you can document adoption date, rationale, failure modes, and whether context has changed. The output is a clear record you can cite when proposing or rejecting changes.

When to use it

• Before proposing to replace or refactor an existing approach
• When dismissing older patterns or reviving a ‘new’ idea
• Before declaring a practice as a team-wide best practice
• When a suggestion triggers: “Why don’t we just…” or “This seems overcomplicated”
• When evaluating major architectural shifts or migrations

Best practices

• Search decision records, ADRs, and docs/decisions before assuming reasons
• Combine git archaeology (git log/git blame) with issue/PR threads for context
• Interview authors or long-time contributors to capture tacit knowledge
• Document findings with concise templates capturing when, why, and context
• Record deliberate overrides so future teams know why history was ignored

Example use cases

• Investigating why a caching layer exists before proposing its removal
• Reassessing a previously failed feature now feasible due to new tools
• Detecting that a ‘new’ pattern is a rebrand of a past approach and learning why it died
• Mapping the trade-offs when shifting from monolith to microservices
• Preparing a proposal that includes lineage to justify a strategic change