create-adr-spike
Create Architecture Decision Records (ADRs) and research spikes for technical decisions. Use when asked to "create an ADR", "architectural decision for", "research spike on", "evaluate options for", "document technical decision", "should we use X or Y", or when analyzing architecture alternatives. Provides structured research, analysis, and documentation workflow with memory storage. Creates .md files in docs/adr/ with proper numbering and status tracking.
npx skills add majiayu000/claude-skill-registry --skill create-adr-spike --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.
# Create ADR Spike Standardized workflow for creating Architecture Decision Records (ADRs) and conducting research spikes for technical decisions. ## Table of Contents ### Core Sections - [Quick Start](#quick-start) - What this skill does and when to use it - [Workflow](#workflow) - Complete 5-phase ADR creation process - [Phase 1: Research (Discovery)](#phase-1-research-discovery) - Gather context and search existing knowledge - [Phase 2: Analysis (Evaluation)](#phase-2-analysis-evaluation) - Evaluate alternatives systematically - [Phase 3: Decision (Recommendation)](#phase-3-decision-recommendation) - Make clear, justified recommendation - [Phase 4: Documentation (Formalization)](#phase-4-documentation-formalization) - Create permanent ADR record - [Phase 5: Memory Storage (Persistence)](#phase-5-memory-storage-persistence) - Store decision in memory graph - [Quality Checklist](#quality-checklist) - Verification before marking spike complete - [Anti-Patterns to Avoid](#anti-patterns-to-avoid) - Common mistakes and correct approaches ### Project Integration - [Project-Specific Conventions](#project-specific-conventions) - ADR directory structure and naming - [Examples](#examples)
- Table of Contents
- Core Sections
- Project Integration
- Supporting Resources
- Additional Information
- Templates
- Quick Start
- Workflow
- Phase 1: Research (Discovery)
- Phase 2: Analysis (Evaluation)
- Phase 3: Decision (Recommendation)
- Phase 4: Documentation (Formalization)
- Phase 5: Memory Storage (Persistence)
- Quality Checklist
find docs/adr -name "*.md" -type f -exec grep -l "keyword" {} \;
find docs/adr -name "[0-9]*.md" | \
sed 's/.*\/\([0-9]*\)-.*/\1/' | \
sort -n | tail -1
Or manually:
find docs/adr -name "[0-9]*.md" | sed 's/.*\/\([0-9]*\)-.*/\1/' | sort -n | tail -1What does the create-adr-spike skill do?
Create Architecture Decision Records (ADRs) and research spikes for technical decisions. Use when asked to "create an ADR", "architectural decision for", "research spike on", "evaluate options for", "document technical decision", "should we use X or Y", or when analyzing architecture alternatives. Provides structured research, analysis, and documentation workflow with memory storage. Creates .md files in docs/adr/ with proper numbering and status tracking.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill create-adr-spike --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.