菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jumbocontext/cli --skill jumbo-add-decision命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when a Jumbo goal needs QA review after implementation. Runs the review protocol, verifies every objective, criterion, and related entity constraint, and approves the goal for codification or rejects it with feedback.
Use when the user's prompt is delivered outside the execution context of an existing Jumbo goal, the prompt is imbued with an objective that is not already defined as a Jumbo goal.
Use when a Jumbo-managed agent file tells the agent to bootstrap the session. Runs Jumbo's session router only when the agent has not already received a routed Jumbo command.
基于 SOC 职业分类
正在显示 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. |
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.