codify-jumbo-goal
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation…
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.
$ npx -y skills add jumbocontext/cli --skill jumbo-add-decision --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/jumbo-add-decisionContext 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.
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.
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.
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>
jumbo decision add \ --title "<Decision title>" \ --context "<Problem statement and background>" \ --rationale "<Why this choice was made>" \ --alternative "<Rejected option>" \ --consequences "<Trade-offs accepted>"
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.
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.
Repo: jumbocontext/jumbo.cli
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation…
Use when a project has Architecture data that needs migrating to fine-grained entities…
Add Jumbo goals liberally to decompose objectives into finite units of work with bounded…
Use when the user's prompt is delivered outside the execution context of an existing Jumbo…
Use liberally when you create, discover, or modify a software component. Registers the…
Use liberally when you introduce, discover, or upgrade a third-party package or external…