Skip to content
Skills Library
Management & product · Planning

decision-log

/decision-log

Records, replaces and disputes the lead's decisions in the hub's decisions/LOG.md. Use when the lead decides something that reaches beyond one task, for /lead-flow:decide, or when an entry looks wrong for the code.

Licence
MIT
Last repository change
04.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Records, replaces and disputes the lead's decisions in the hub's decisions/LOG.md. Use when the lead decides something that reaches beyond one task, for /lead-flow:decide, or when an entry looks wrong for the code.

Triggers from the description

s decisions in the hub
Original author description

Records, replaces and disputes the lead's decisions in the hub's decisions/LOG.md. Use when the lead decides something that reaches beyond one task, for /lead-flow:decide, or when an entry looks wrong for the code.

How it works

  1. Add an entry
  2. Replace, never edit away
  3. Dispute
Original SKILL.md headings · 44 lines, 283 words
SKILL.md preview
---
name: decision-log
description: Records, replaces and disputes the lead's decisions in the hub's decisions/LOG.md. Use when the lead decides something that reaches beyond one task, for /lead-flow:decide, or when an entry looks wrong for the code.
---

# Decision log

`decisions/LOG.md` holds every decision the lead makes, from the design on. An `active` entry
beats the design and the task files.

## Add an entry

Append, with the next free number:

```markdown
### L-NNN · YYYY-MM-DD · active
Decided in: <task id, "lead session" or "setup"> · Replaces: <the entry, design line or task-file line, or —>
Decision: <what is now true, concrete: column, route, rule>
Reason: <the lead's reason, in the lead's words where you have them>
Affects: <task ids, and for each what changes>
Disputes:
```

Then:

1. In each affected task file that has not started, add under "Decisions to re-check":
   `- **L-NNN** (decision log): <one line>; check it still fits your code.` Message the running
   ones (the `messages` skill).
2. After pulling, check your number is not used twice. If it is, renumber **your** entry to the
   next free number and fix your references.
3. Commit in the hub: `docs(decisions): L-NNN <summary>`.

## Replace, never edit away

An entry is never edited or deleted. To change a decision, add a new entry whose `Replaces:` names
the old one, and change the old entry's status to `superseded by L-NNN`: the only edit an old entry
allows.

A superseded setup record (`Decided in: setup`) goes to the coordinator's `## The project's
shape`, which runs the for-others or removal step. That covers `/lead-flow:decide` too.

## Dispute

An entry looks wrong for the code: add a line under its `Disputes:`
(`date · task · what you found (verified names) · what you propose`), raise it with the lead, and
build only what doesn't depend on it. The lead answers with a new entry, or a `kept:` line and a
reason.

Versions

RepositoryScoreLicence
This page · M-reza-kd/lead-flow-plugin100MIT
cravingmaker/skills100MIT
moonlight-lupin/agent-skills100MIT
shrwnsan/vibekit-claude-plugins100Apache-2.0
khaledsaeed18/dotclaude100MIT
xdg/xdg-claude100Apache-2.0
KirKruglov/claude-skills-kit100MIT
diegopacheco/ai-playground90Unlicense
erica-j-01/ai-pm90MIT

Database snapshot: 13.11.2026 · package version c06fda328583 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90decide
    Records a decision in Claude/Decisions.md after checking it against earlier decisions, with the reason and a note of anything it replaces. Use it for "we're going with X", "log this decision", "help me choose between A and B", or when work reaches a choice that future sessions must follow.
  • 86log-decision
    Record a decision or an accepted risk in the decision log. Use when the owner or the team makes a decision.
  • 90sage-decisions
    Recording decisions in the right log. Use when a decision needs to be written down, when the user asks why something was decided, when writing an ADR or a decision entry, or when unsure whether something belongs in the initiative's log or the global one.
  • 100bundle
    Cuts a teammate's own hub out of the lead's for the repos they take over - their unfinished tasks, the pending notes those tasks own, wave logs, decisions, design notes, context packs and plugin settings - then shows the lead's hub change and commits it. Use for…
  • 100close
    Closes tasks that are ready_to_close. Dispatches one close-agent per repo in parallel (a hub task is closed by the skill itself), shows the results, merges only on the lead's yes, then records the merge in the wave log and the status block. Use for /lead-flow:close, or when a…
  • 100decide
    Record, revise, or supersede one decision in a trajectory project's decision log. Takes a statement to decide on, a reference to an existing decision (to revise or supersede), or — when invoked empty — the next open decision item from the lowest-id open milestone. Runs a brief…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.