Memory Decide

Creates structured ADRs with sequential numbering for project decisions.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/whjelmar/claude-memory-system --skill memory-decide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Memory Decide
Source: https://github.com/whjelmar/claude-memory-system/tree/main/skills/memory-decide
Command: npx skills add https://github.com/whjelmar/claude-memory-system --skill memory-decide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you systematically record and document significant architectural and design decisions made during a project, ensuring clarity and historical context.

Core Features & Use Cases

  • Decision Record Creation: Generates structured decision records (ADRs) in a standardized format.
  • Numbered Decisions: Automatically assigns sequential numbers to decisions for easy referencing.
  • Use Case: When deciding on a new database technology, use this skill to document the problem, the options considered (e.g., PostgreSQL vs. MongoDB), the final choice, and the reasoning behind it.

Quick Start

Use the memory decide skill to create a new decision record for using JWT for API authentication.

Frequently Asked Questions about Memory Decide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an architectural decision record and when do I need one?

An architectural decision record (ADR) documents significant technical choices made during a project. You need an ADR when making architectural or design decisions, such as selecting a database technology, to ensure clarity and preserve historical context for future reference.

How do I document technical decisions and the reasoning behind them?

You document technical decisions by creating structured decision records that capture the problem context, options considered, chosen solutions, and consequences. This systematic recording ensures clarity and tracks the technical evolution of your architecture over time.

How do I create a numbered ADR for a new software architecture choice?

To create a numbered ADR, the skill scans your existing decision files to determine the next sequential number and generates a new structured file in a specified directory. This automatically assigns sequential numbers for easy referencing and tracking.

Does this method for documenting technical decisions require any specific frameworks?

Documenting technical decisions with this skill requires no specific frameworks or dependencies. It focuses on generating standardized files to record architectural choices within your project, requiring only a specified directory to save the output.

What is the best way to track architectural changes and design choices over time?

The best way to track architectural changes is by creating structured decision records that capture the context, options considered, and chosen solutions. This facilitates tracking of technical evolution by providing a clear historical log of design choices and their consequences.