adr-decision-extraction
Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit \"[ADR]\" tags. Triggers on \"what decisions did we make\", \"extract decisions from this chat\", \"find the choices in our discussion\", or \"summarize architectural decisions\". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents \u2014 use adr-writing or write-adr for that.
npx skills add majiayu000/claude-skill-registry --skill adr-decision-extraction --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ADR Decision Extraction Extract architectural decisions from conversation context for ADR generation. ## Detection Signals | Signal Type | Examples | |-------------|----------| | Explicit markers | `[ADR]`, "decided:", "the decision is" | | Choice patterns | "let's go with X", "we'll use Y", "choosing Z" | | Trade-off discussions | "X vs Y", "pros/cons", "considering alternatives" | | Problem-solution pairs | "the problem is... so we'll..." | ## Extraction Rules ### Explicit Tags (Guaranteed Inclusion) Text marked with `[ADR]` is always extracted: ``` [ADR] Using PostgreSQL for user data storage due to ACID requirements ``` These receive `confidence: "high"` automatically. ### AI-Detected Decisions Patterns detected without explicit tags require confidence assessment: | Confidence | Criteria | |------------|----------| | **high** | Clear statement of choice with rationale | | **medium** | Implied decision from action taken | | **low** | Contextual inference, may need verification | ## Output Format ```json { "decisions": [ { "title": "Use PostgreSQL for user data", "problem": "Need ACID transactions for financial records", "chosen_option": "PostgreSQL", "alternatives_discussed":
- Detection Signals
- Extraction Rules
- Explicit Tags (Guaranteed Inclusion)
- AI-Detected Decisions
- Output Format
- Field Definitions
- Extraction Workflow
- Hard gates
- Pattern Examples
- High Confidence
- Medium Confidence
- Low Confidence
- Best Practices
- Context Capture
What does the adr-decision-extraction skill do?
Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit \"[ADR]\" tags. Triggers on \"what decisions did we make\", \"extract decisions from this chat\", \"find the choices in our discussion\", or \"summarize architectural decisions\". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents \u2014 use adr-writing or write-adr for that.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill adr-decision-extraction --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.