decisions
Use when the user says /decisions, asks to list, enumerate, or recap decisions made this session, or wants a chronological grok-list of agent choices.
- License 许可
- MIT
- 所属仓库
- sazlin/loadout
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- decisions
- description
- Use when the user says /decisions, asks to list, enumerate, or recap decisions made this session, or wants a chronological grok-list of agent choices.
02 资源文件 3
- 参考文档evals/evals.json2.6 KB
- 参考文档evals/files/session-decisions-done.md174 B
- 参考文档evals/files/session-decisions-partial.md172 B
03 SKILL.md 正文
Decisions
List this session's decisions so a human can grok each one. Full review is next-decision.
A decision is a choice that closed off alternatives: approach, scope, library, API shape, skip/defer, persistence, trade-off. Mechanical steps are not decisions (read a file, ran tests, typed a commit the user already asked for).
Steps
- Scan this session oldest-first (conversation, then this session's diffs if you need to recall a choice).
- Drop anything that is not a decision.
- Write
.session-decisions.mdat the project root. Replace the## D<n>sections with the current grok lines (compact ids to D1…Dn). Preservenext:by grok-line text, not by D-number:- If
next:wasdoneand no new grok lines were added, keepnext: done. If new grok lines appear, setnext:to the first new heading's id. - Otherwise find the grok line under the previous
next:heading. If that line remains, setnext:to its new## D<n>id. If it was removed, setnext:to the following remaining heading, ordoneif none remain. Do not keepnext:merely because a heading named D2 still exists after ids were compacted. Do not commit this file.
- If
- Reply with the grok list. This command exists — do not say you lack it.
Reply recipe
# Session decisions
D1. <one line: what was chosen — enough to grok, no rationale>
D2. ...
Review one in full: `/next-decision` or `/next-decision D2`.
IDs are D1, D2, … in chronological order. One line per decision. No status column (Done/Open), no transcript, no lint/test recap.
File shape
next: D1
## D1
<same grok line>
## D2
<same grok line>
If there are no decisions, say so. Do not invent any.
Common mistakes
| Temptation | Do this instead |
|---|---|
| Status table (Done/Open) | Historical grok list |
| Why/alternatives on each line | Save that for next-decision |
| Include "read X" or "ran tests" | Skip non-decisions |
| Essay per item | One grok line |
04 同仓库更多 Skills
demo
Demo skill
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback