Our review

Creates and updates Architecture Decision Records (ADR) to document significant architectural decisions for the ABIOGENESIS project.

Strengths

Clear structure with a predefined template (ADR-XXX) and step-by-step instructions.
Includes an index and checklist to ensure completeness.
Guidance on when to create an ADR (framework, database, refactoring) and when to skip.
Supports status updates and cross-referencing.

Limitations

Specific to the ABIOGENESIS project (`docs/architecture/` directory).
Requires prior knowledge of ADR format for optimal use.
File numbering must be done manually (no auto-increment).

When to use it

Use this skill when you need to record a major architectural decision (framework choice, database, integration pattern) within the project.

When not to use it

Avoid using it for minor fixes, incremental improvements, or decisions that have no lasting architectural impact.

Examples

Create ADR for database choice

Create a new ADR for our decision to adopt PostgreSQL as the primary database for ABIOGENESIS. Use the ADR template from the skill and suggest the next ADR number based on existing records.

Update ADR status to Accepted

Update ADR-002 (Scarlet Setup) status to 'Accepted' and add a 'Last Updated' date of today. Also check the checklist to ensure all sections are filled.

List all ADRs with status

List all Architecture Decision Records in the ABIOGENESIS project and show their statuses in a table.

name: adr description: Create and update Architecture Decision Records for ABIOGENESIS

ADR (Architecture Decision Record) Skill

Purpose

Maintain architectural documentation using the ADR format for significant decisions.

When to Create an ADR

Create an ADR when decisions involve:

Framework or tool selection (e.g., Letta adoption)
Database or storage choices
Integration patterns
Major refactoring
Technology stack changes

Small fixes and incremental improvements don't need ADRs.

ADR Template

See docs/architecture/adr-template.md for the full template, but use this structure:

# ADR-XXX: Descriptive Title

**Status**: [Proposed | Accepted | Deprecated | Rejected]
**Date**: YYYY-MM-DD
**Author**: Claude Code

## Context
[Why do we need to make this decision?]

## Decision
[What have we decided to do?]

## Consequences
### Positive
- [Benefits]

### Negative
- [Drawbacks]

### Neutral
- [Trade-offs]

## Alternatives Considered
- [Option]: Why rejected

## References
- [Links]

Usage

Create new ADR

# Check next number
ls docs/architecture/adr-*.md | sort

# Copy template
cp docs/architecture/adr-template.md docs/architecture/adr-XXX-title.md

Update Status

When implementing or deprecating:

Open the ADR
Change Status header
Add Last Updated date

ADR Index

| Number | Title | Status | |--------|-------|--------| | ADR-001 | Letta Framework Adoption | Accepted | | ADR-002 | Scarlet Setup (Foundation + Embeddings) | Accepted |

Checklist

[ ] Filename: adr-XXX-title.md
[ ] Status valid
[ ] All sections filled
[ ] CHANGELOG.md updated

Architecture Decision Records (ADR)

Recommended for