What problem does it solve? Architectural decisions made during coding sessions often live only in chat threads, PR comments, or someone's memory, leaving future developers wondering why the codebase is shaped the way it is. This Skill records those decisions as structured ADR documents stored alongside the code. ## Core Features & Use Cases - Decision Detection: Recognizes explicit signals ("let's go with X") and implicit signals (framework comparisons, pattern trade-offs) that indicate a recordable architectural decision. - Structured ADR Writing: Produces lightweight Nygard-style ADRs covering context, decision, alternatives considered, and consequences, saved to .farseer/adr/ with sequential numbering. - ADR Index and Lookup: Maintains a README index of all ADRs and answers "why did we choose X?" questions by reading existing records. - Use Case: While debating PostgreSQL versus MongoDB for a new service, you settle on PostgreSQL for relational integrity. The Skill drafts ADR-0002 documenting the rejected alternative and trade-offs, then updates the index after your approval. ## Quick Start Ask the assistant to record the database choice we just discussed as an architecture decision record.