Extract architectural decisions from conversations. Identifies problem-solution pairs, trade-off discussions, and explicit choices. Use when analyzing session transcripts for ADR generation.
Extracts architectural decisions from conversations by identifying problem-solution pairs, trade-offs, and explicit choices. Triggers when analyzing session transcripts for ADR generation or reviewing discussion history for documentation.
/plugin marketplace add existential-birds/beagle/plugin install beagle@existential-birdsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Extract architectural decisions from conversation context for ADR generation.
| 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..." |
Text marked with [ADR] is always extracted:
[ADR] Using PostgreSQL for user data storage due to ACID requirements
These receive confidence: "high" automatically.
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 |
{
"decisions": [
{
"title": "Use PostgreSQL for user data",
"problem": "Need ACID transactions for financial records",
"chosen_option": "PostgreSQL",
"alternatives_discussed": ["MongoDB", "SQLite"],
"drivers": ["ACID compliance", "team familiarity"],
"confidence": "high",
"source_context": "Discussion about database selection in planning phase"
}
]
}
| Field | Required | Description |
|---|---|---|
title | Yes | Concise decision summary |
problem | Yes | Problem or context driving the decision |
chosen_option | Yes | The selected solution or approach |
alternatives_discussed | No | Other options mentioned (empty array if none) |
drivers | No | Factors influencing the decision |
confidence | Yes | high, medium, or low |
source_context | No | Brief description of where decision appeared |
[ADR] tagged content"We decided to use Redis for caching because of its sub-millisecond latency
and native TTL support. Memcached was considered but lacks persistence."
Extracts:
"Let's go with TypeScript for the frontend since we're already using it
in the backend."
Extracts:
"The API seems to be working well with REST endpoints."
Extracts:
Always capture sufficient context for the ADR writer:
If multiple statements relate to the same decision, consolidate them:
When decisions are unclear or contradictory:
source_contextlowUse when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.