| name | decision-log |
| description | Surface past decisions, their reasoning, and outcomes to inform a current decision — and log new decisions so they're not relitigated later. Use this skill whenever the user faces a hard decision, wants to avoid repeating past mistakes, asks what was decided about something before, or wants to think through a tradeoff with full context of prior commitments. Also trigger when someone says they keep going in circles on something, or wants a structured way to make and record a decision. |
Decision Log
Two jobs: (1) pull relevant past decisions from Unabyss before making a new one, and (2) structure and record the new decision so it can be referenced later.
Required Integrations
This skill uses Unabyss MCP — query for past decisions, store to log new ones.
If Unabyss is not connected, tell the user: "This skill requires Unabyss MCP. You can connect it from the Tools menu."
How to Run
Step 1 — Pull prior decisions with query
Past decisions are explicit, specific facts — query is sufficient:
Look across all connected sources for past decisions relevant to [topic/area]. Find: explicit decisions that were made and the reasoning given, constraints or principles established, things that were tried and abandoned, and any commitments made to the team, customers, or investors that bear on this.
If prior decisions directly resolve the current question, surface that immediately and stop.
Step 2 — Structure the current decision
The decision — one clear sentence: what exactly is being decided.
Why now — what's forcing this decision.
Options — 2–4 realistic ones only. For each:
- What it means in practice
- The upside if it works
- The downside or risk
- What it forecloses
What prior decisions rule anything out — from Step 1.
The recommendation — a clear position and the single most important reason. If genuinely too close to call, name the one question that would resolve it.
What to watch — 1–2 signals that would indicate the decision was wrong.
Step 3 — Log the decision with store
Once the user confirms a decision, call store to persist it:
[Decision] — [Date]. We decided to [option]. The main reason was [reasoning]. We considered [alternatives] but ruled them out because [brief explanation]. We'll revisit if [trigger condition].
This ensures future query calls surface this decision as prior context.
Output Rules
- Use
query for past decisions — fast and specific, no need for agentic_query
- Always call
store after a decision is confirmed — closing the loop is the point
- If prior decisions resolve the question, say so rather than running the full framework
- Never make the decision for the user — structure it, recommend, but the call is theirs
- No preamble before the output
