decision-loglisted

# Decision Log Persist design and architectural decisions as ADR (Architecture Decision Record) files. Arguments: `$ARGUMENTS` - decision title or description, or `list` to show all decisions, or `search <term>` to find related decisions ## Behavior ### 1. Route by Mode ```bash # Detect mode from arguments if [[ "$ARGUMENTS" == "list" ]]; then ls -t docs/decisions/*.md 2>/dev/null | head -20 || echo "No decisions recorded yet." exit 0 fi if [[ "$ARGUMENTS" == search* ]]; then TERM="${ARGUMENTS#search }" grep -rn "$TERM" docs/decisions/ 2>/dev/null | head -20 exit 0 fi ``` ### 2. Initialize Decisions Directory ```bash mkdir -p docs/decisions # Check for existing ADRs to get next sequence number LAST=$(ls docs/decisions/*.md 2>/dev/null | grep -o '[0-9]\{4\}' | sort -n | tail -1) NEXT=$(printf "%04d" $(( ${LAST:-0} + 1 ))) DATE=$(date +%Y-%m-%d) ``` ### 3. Generate ADR File Filename: `docs/decisions/NNNN-<slugified-title>.md` ```markdown # NNNN. [Decision Title] **Date**: YYYY-MM-DD **Status**: Proposed | Accepted | Rejected | Deprecated | Superseded by [NNNN] **Deciders**: [names or teams] ## Context [What is the issue motivating this decision? What forces are at play — technical, business, schedule? Include relevant constraints. 2-4 sentences.] ## Decision [The change being proposed or that was made. State it as a full sentence starting with "We will..."] ## Alternatives Considered ### Option A: [Name] (chosen) - Pros: ... - Cons: ... ### Option