Skip to content
Agent Memory
Skill

/jumbo-add-decision

Use liberally when you make an architectural choice, select a technology, or reject an alternative. Records the decision so future sessions understand why the codebase looks the way it does.

From plugin
jumbocli
26518 skills
Install
$ npx -y skills add jumbocontext/jumbo.cli --skill jumbo-add-decision --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/jumbo-add-decision

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use liberally when you make an architectural choice, select a technology, or reject an alternative. Records the decision so future sessions understand why the codebase looks the way it does.

SKILL.md

jumbo-add-decision.SKILL.md
name: jumbo-add-decision
description: Use liberally when you make an architectural choice, select a technology, or reject an alternative. Records the decision so future sessions understand why the codebase looks the way it does.

Add Decision

Register an architectural decision with Jumbo when you choose one approach over alternatives. Decisions explain **why** the codebase looks the way it does — without them, future agents may reverse your choices or repeat your analysis.

Before Adding

Check for an existing decision to avoid duplication. Consider reversing, updating, or superseding a previously registered decision before registering a new one.

Use the search subcommand to locate previously registered decisions:

jumbo decisions search -q <query>

Command Syntax

jumbo decision add \
  --title "<Decision title>" \
  --context "<Problem statement and background>" \
  --rationale "<Why this choice was made>" \
  --alternative "<Rejected option>" \
  --consequences "<Trade-offs accepted>"

Bad Example

jumbo decision add \
  --title "Use events" \
  --context "Need to track changes"

Title is too vague to be useful. Missing rationale means a future agent has no basis for understanding the choice. Missing alternatives means they cannot evaluate whether the context has changed.

Good Example

jumbo decision add \
  --title "Use event sourcing over state-based persistence for domain aggregates" \
  --context "Domain aggregates need audit history and the ability to rebuild state at any point in time" \
  --rationale "Event sourcing provides a complete audit trail and enables temporal queries without additional infrastructure" \
  --alternative "State-based persistence with a separate audit log table" \
  --consequences "Requires projection rebuilding for read models; increases storage for high-frequency aggregates"

Title names both the chosen and rejected pattern. Context explains the problem. Rationale connects the choice to the problem. Alternatives and consequences give future agents the information they need to judge whether the decision still holds.

Read more
Ships withjumbocli

Memory and Context Orchestration for Coding Agents

Get the whole plugin