architecture-decision-records

原文涵盖的主题

• Architecture Decision Records
• When to Activate
• ADR Format
• Workflow
• Capturing a New ADR
• Reading Existing ADRs
• ADR Directory Structure
• ADR Index Format

Capture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code. User explicitly says "let's record this decision" or "ADR this" User chooses between significant alternatives (framework, library, pattern, database, API design) User says "we decided to..." or "the reason we're doing X instead of Y is..." User asks "why did we choose X?" (read existing ADRs) During planning phases when architectural trade-offs are discussed Use the lightweight ADR format proposed by Michael Nygard, adapted for AI-assisted development: When a decision moment is detected: 1. Initialize (first time only) — if docs/adr/ does not exist, ask the user for confirmation before creating the directory, a README.md seeded with the index table header (see ADR Index Format below), and a blank template.md for manual use. Do not create files without explicit consent. 2. Identify the decision — extract the core architectural choice being made 3. Gather context — what problem prompted this? What constraints exist? 4. Document alternatives — what other opt

这里只展示节选，请以完整原文和当前要求为准。