Log decision

What this is for

A decision that lives only in a Slack thread or someone's memory is a decision the team will re-litigate in three months. This skill writes a settled decision into Jupi as a FINALIZED record — so it surfaces later via search-decisions with its rationale attached. Think of it as the "commit message" for a choice: quick to write in the moment, valuable forever after.

Use it for calls that are made. If the question is still open and someone else needs to decide, that's submit-decision, not this.

The shape of the underlying tools

Jupi's model is: a decision is created in STARTED state with options on its board, then finalize closes it by recording which option(s) won. To log an already-made decision, you walk that same path in one sitting: create the decision, create the chosen path as a real option on the board, then finalize selecting it. The record reads exactly like a decision made in the app — a populated board with the winner marked — and its rationale lives in closingText.

Tools you'll use

Provided by the Jupi MCP server (may appear namespaced as mcp__Jupi__… or mcp__claude_ai_Jupi__…):