log-decision

Name: log-decision
Author: chacosoldier

29stars6forks

How to install log-decision?

chacosoldier/compabob/log-decision

$npx -y skills add chacosoldier/compabob --skill log-decision

Installs into the current project.

Summary

Record a strategic decision with its reasoning, the alternatives considered, and a date to review the outcome. Use for "/log-decision", "log this decision", or after a significant choice is made.

Files · 1

View on GitHub

SKILL.md

1	# Log Decision
2
3	Capture a decision while the reasoning is fresh, so it can be reviewed honestly later. The point is calibration: a decision logged with its expected outcome can be checked against what actually happened.
4
5	## Steps
6
7	1. Gather the decision: what was decided, when, and by whom.
8	2. Capture the reasoning: the key factors, and the single most important one.
9	3. Capture the alternatives: what else was on the table, and why it lost. "Do nothing" counts.
10	4. State the expected outcome and a review date (usually 30 to 90 days out).
11	5. Write to `vault/Decisions/YYYY-MM-DD-<slug>.md`.
12
13	## Format
14
15	```
16	---
17	title: [decision]
18	date: YYYY-MM-DD
19	review_on: YYYY-MM-DD
20	status: open
21	tags: [decision]
22	---
23
24	# [Decision]
25
26	Decision: [what was decided]
27
28	Why: [the reasoning, most important factor first]
29
30	Alternatives considered:
31	- [option] — rejected because [...]
32
33	Expected outcome: [what success looks like, concretely]
34
35	Review on <review-date>: _(left blank until the review)_
36	```
37
38	## Reviewing
39
40	When `/log-decision review` is run, list decisions whose `review_on` date has passed, and for each ask: did it work out? Fill in the review section and set `status` to `validated`, `mixed`, or `wrong`. Honest reviews are the whole value.

People who liked this also viewed

6 picks

Type

azure-diagnosticsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deploySkillsJul 2026472k1.3k
systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesSkillsJul 2026197k259k
safe-debugRigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training SkillsMay 2026161k507
explore-runRigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subseSkillsMay 2026161k507
minimal-run-and-auditRigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation SkillsMay 2026161k507
insforge-debugUse when diagnosing problems in an InsForge project — reactive failures (SDK error object, HTTP 4xx/5xx, gateway timeout 502/503/504, edge function failure or timeout, login/OAuth/auth errors, RLS denSkillsJul 202618k31

log-decision

29stars6forks

View on GitHub

How to install log-decision?

chacosoldier/compabob/log-decision

$npx -y skills add chacosoldier/compabob --skill log-decision

Installs into the current project.

Summary

Record a strategic decision with its reasoning, the alternatives considered, and a date to review the outcome. Use for "/log-decision", "log this decision", or after a significant choice is made.

Files · 1

View on GitHub

SKILL.md

1	# Log Decision
2
3	Capture a decision while the reasoning is fresh, so it can be reviewed honestly later. The point is calibration: a decision logged with its expected outcome can be checked against what actually happened.
4
5	## Steps
6
7	1. Gather the decision: what was decided, when, and by whom.
8	2. Capture the reasoning: the key factors, and the single most important one.
9	3. Capture the alternatives: what else was on the table, and why it lost. "Do nothing" counts.
10	4. State the expected outcome and a review date (usually 30 to 90 days out).
11	5. Write to `vault/Decisions/YYYY-MM-DD-<slug>.md`.
12
13	## Format
14
15	```
16	---
17	title: [decision]
18	date: YYYY-MM-DD
19	review_on: YYYY-MM-DD
20	status: open
21	tags: [decision]
22	---
23
24	# [Decision]
25
26	Decision: [what was decided]
27
28	Why: [the reasoning, most important factor first]
29
30	Alternatives considered:
31	- [option] — rejected because [...]
32
33	Expected outcome: [what success looks like, concretely]
34
35	Review on <review-date>: _(left blank until the review)_
36	```
37
38	## Reviewing
39
40	When `/log-decision review` is run, list decisions whose `review_on` date has passed, and for each ask: did it work out? Fill in the review section and set `status` to `validated`, `mixed`, or `wrong`. Honest reviews are the whole value.

People who liked this also viewed

6 picks

Type