goals-decision-explainer

Étoiles14

Forks4

Mis à jour14 juin 2026 à 06:17

Explain a project decision from the active Goals goal in plain language — what needs the user, the recommended reply, and what happens next. Use inside a Goals project when a technical decision, risk, or tradeoff needs a non-technical explanation, or when deciding whether a choice should interrupt the user.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

ShivamGupta42

ShivamGupta42/goals

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	goals-decision-explainer
description	Explain a project decision from the active Goals goal in plain language — what needs the user, the recommended reply, and what happens next. Use inside a Goals project when a technical decision, risk, or tradeoff needs a non-technical explanation, or when deciding whether a choice should interrupt the user.

Goals Decision Explainer

Ships with the Goals CLI. Works inside a Goals project (a goal worktree with active state created by goals start).

When to use

A technical decision, migration, or high-risk tradeoff needs a plain-language explanation for a non-technical user.
You need to know whether a choice should interrupt the user or can stay with the agent.

How to run

Start with the compact brief (zero-arg, reads the active goal):
```
goals decision brief
```
It shows only choices that need the user, the recommended reply, what happens after, and how many routine choices can stay with the agent.

To explain one specific decision file at a chosen depth:

goals decision explain --file decision.json --level basic   # or detailed, technical

If there is no active Goals goal, this skill does not apply — run it from a goal worktree created by goals start.

Plus depuis ce dépôt

même dépôt

goals-critique

ShivamGupta42/goals

Run a retrospective on a completed (or stalled) Goals goal to learn from it — critique both the engine/UX friction the CLI created AND the agent's own execution quality, record durable lessons into self-evolution memory, surface cross-goal patterns, and file engine friction upstream. Use after `goals check` reports a goal complete, after a painful or stalled goal, or periodically to learn across every goal you run.

2026-06-2214

goals-problem-solving

ShivamGupta42/goals

Solve a problem or define/break down a goal using PACERS (Pause, Assess, Choose, Execute, Review, Systemize) and record the reasoning as a traceable building journey in the active Goals goal. Use inside a Goals project when defining a goal, breaking a phase into sub-problems, hunting assumptions before building, or whenever a problem is recurring, costly, unclear, or likely to create second-order effects.

2026-06-2114

goals-architecture-diagram

ShivamGupta42/goals

Generate a clean architecture or loop diagram for the active Goals goal as Mermaid or a valid .excalidraw file. Use when the user asks to visualize, diagram, or draw the goal's architecture map or the designed loop.

2026-06-1414

goals-architecture-map

ShivamGupta42/goals

Show the architecture map of the active Goals goal — what is built, planned, blocked, deferred, or missing. Use inside a Goals project when you need the system shape, a diagram-style overview, or to check recorded changes against the goal's architecture.

2026-06-1414

name	goals-decision-explainer
description	Explain a project decision from the active Goals goal in plain language — what needs the user, the recommended reply, and what happens next. Use inside a Goals project when a technical decision, risk, or tradeoff needs a non-technical explanation, or when deciding whether a choice should interrupt the user.

Goals Decision Explainer

Ships with the Goals CLI. Works inside a Goals project (a goal worktree with active state created by goals start).

When to use

A technical decision, migration, or high-risk tradeoff needs a plain-language explanation for a non-technical user.
You need to know whether a choice should interrupt the user or can stay with the agent.

How to run

Start with the compact brief (zero-arg, reads the active goal):
```
goals decision brief
```
It shows only choices that need the user, the recommended reply, what happens after, and how many routine choices can stay with the agent.

To explain one specific decision file at a chosen depth:

goals decision explain --file decision.json --level basic   # or detailed, technical

If there is no active Goals goal, this skill does not apply — run it from a goal worktree created by goals start.