菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Use when an agent needs to discover Jumbo command syntax after session routing. Directs command discovery through CLI help instead of static command catalogs.
Use when implementation discovers durable project context that must be recorded in Jumbo. Captures decisions, components, dependencies, relations, guidelines, and invariants during the work.
Use when the user corrects an approach, constraint, workflow, or style. Converts corrections into Jumbo guidelines or invariants so future sessions receive the constraint.
Use when a Jumbo goal has been approved by QA review and needs architectural reconciliation before closing. Captures new learnings, updates stale entities, and ensures documentation reflects the work performed.
| 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.