forge-decisionlisted

# forge-decision Record architecture decisions as lightweight ADRs (Architecture Decision Records) so the "why" behind the system is never lost. Decisions live in `context/decisions.md`. ## Argument Text after the command is the decision (e.g. `/forge-decision use Redis for the cache instead of in-memory`) — draft the ADR from it directly, asking only for missing context/consequences. No argument → ask what was decided and why. For a decision with broad blast radius (storage model, boundary change, framework swap), delegate the analysis to the `forge-architect` agent (opus-pinned) first — it returns an ADR-shaped analysis (context, options with trade-offs, recommendation, consequences) to draft from. Small decisions don't need it. ## When to log Log a decision whenever the project makes a choice that shapes the system and would be expensive or confusing to reverse silently: picking/replacing a technology, changing a boundary or storage model, adding or changing an invariant, choosing a pattern that other code must follow. ## How 1. If `context/decisions.md` doesn't exist, create it from the bundled template at `${CLAUDE_PLUGIN_ROOT}/skills/forge-decision/templates/decisions.md`. 2. Determine the next ADR number (increment the highest existing one). 3. Append a new entry using this structure: ``` ## ADR-NNN: <short title> - **Date:** YYYY-MM-DD - **Status:** Accepted <!-- Proposed | Accepted | Superseded by ADR-XXX --> ### Context What forces are at play —