agentsclimarketplace

Decision log

Skill janellecipriano/pm-skills/skills/decision-log

Open-source Claude skills for Program Management in product development — charters, status reports, RAID logs, roadmaps, launch readiness, retros, postmortems, OKRs & more.

Install
npx -y skills add janellecipriano/pm-skills --skill decision-log

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Capture decisions in a durable, searchable log — the decision, context, options considered, rationale, owner, and date. Use when the user says "log this decision", "decision record", "ADR", "document what we decided", "decision log", or wants to record why a choice was made so it isn't relitigated later.

SKILL.md

2.0 KB, as published. Nobody here has run it

Decision Log

Record decisions (and why) so the team has a single source of truth and stops relitigating settled questions.

When to use

  • A meaningful decision was made (technical, product, process, scope, prioritization).
  • Writing or maintaining a decision log / ADR (Architecture/Any Decision Record) set.

Inputs to gather

  • The decision itself, in one sentence.
  • The context/problem that forced a choice.
  • Options considered and why the chosen one won (and others lost).
  • Who decided, who was consulted, and the date.

Process

  1. State the decision as a clear, active sentence ("We will ...").
  2. Capture context — what made this necessary, constraints, deadline.
  3. List options considered with the key trade-off of each, and mark the chosen one.
  4. Give the rationale — why this option, including what you're explicitly accepting as a downside.
  5. Note status (Proposed / Accepted / Superseded), decider, stakeholders consulted, and date.
  6. Record consequences / follow-ups and link any decision this supersedes.

Output format — one record per decision

### {{ID}}: {{Decision title}}
- **Status:** Accepted · **Date:** {{date}} · **Decider:** {{name}} · **Consulted:** {{names}}
- **Context:** {{why a decision was needed}}
- **Decision:** We will {{decision}}.
- **Options considered:**
  - {{Option A}} — {{trade-off}}  ✅ chosen
  - {{Option B}} — {{trade-off}}
- **Rationale:** {{why, including accepted downsides}}
- **Consequences / follow-ups:** {{what changes; tasks created}}

Keep records append-only: supersede rather than edit history.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.