Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Decision Log

ASecurity

Record an important decision so a later reader can see the choice, the alternatives, and what would reopen it. Use when the user mentions decision log, document this decision, why did we choose, decision record, or asks for a decision record. Strategy and leadership skill by Yasir Jilani.

2 stars
0 votes
0 copies
1 views
Added 9/30/2026
ai-agentspythonawsgitapi

Works with

cliapi

Security Analysis

A100/100

Scanned 9/30/2026

$npx -y skills add SYasJ/claude-business-skills --skill decision-log --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Decision Log?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Decision Log
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/syasj-decision-log/badge)](https://www.skillsdirectory.com/skills/syasj-decision-log)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: decision-log
description: "Record an important decision so a later reader can see the choice, the alternatives, and what would reopen it. Use when the user mentions decision log, document this decision, why did we choose, decision record, or asks for a decision record. Strategy and leadership skill by Yasir Jilani."
license: MIT
compatibility: Agent Skills standard. No network access, extra packages, or credentials required.
metadata:
  author: Yasir Jilani
  version: "1.0.0"
  domain: strategy
---

<!-- GENERATED FILE - edits here are overwritten by scripts/generate.py.
     Edit the 'decision-log' entry in source/, then run:
       python3 scripts/generate.py && python3 scripts/validate.py
     See CONTRIBUTING.md. -->

# Decision Log

Record an important decision so a later reader can see the choice, the alternatives, and what would reopen it.

## When to use this skill

Use this skill when the user:

- decision log
- document this decision
- why did we choose
- decision record
- ADR for the business

## When not to use this skill

- The user wants a different domain's specialist skill.
- The task requires a licensed professional to decide, and the user only needs a referral note rather than a draft.
- The request asks you to deceive, evade a control, or hide material facts.

## Professional boundary

Strategy work recommends a direction. It does not guarantee market outcomes.

## Operating boundaries

- Use only information the user provides or files they explicitly ask you to read. Do not invent metrics, laws, citations, prices, credentials, or clinical facts.
- Do not ask for passwords, API keys, tokens, seed phrases, one-time codes, or payment card data.
- Do not send data to an external service, install packages, or add network calls as part of this skill.
- Separate facts, assumptions, and recommendations. If a required input is missing, state the assumption or ask one focused question.
- If the user asks you to deceive a person, evade a control, forge a record, or cause harm, stop. Offer a legitimate alternative.
- Work product that affects money, employment, health, safety, or legal rights is a draft for a qualified human to review before it is used.

## Inputs to collect

- The decision in one sentence
- Alternatives considered
- Facts used
- Who decided and when

## Workflow


### 1. State the decision

One sentence, past or present tense, with the date and the decider. No preamble.
### 2. Record alternatives

At least one real alternative that was rejected, and why. If none was considered, say that plainly.
### 3. Cite facts

List only evidence the user provided. Do not backfill a rationale that sounds smarter than the actual one.
### 4. Name the reopen condition

What new fact would justify revisiting the decision. Decisions without reopen conditions become dogma.
### 5. Note consequences

Who must change what by when because of this decision.
### 6. File it

Suggest a location and a title the team can find later. Do not create a new bureaucracy around the log.

## Output

Deliver a **decision record**.

- Purpose of this decision record, in two sentences.
- Facts the user supplied, listed separately from assumptions.
- The work itself, in the structure the workflow names.
- Open questions, risks, and the single next action with an owner.
- What a qualified reviewer still needs to confirm, if the domain is regulated.

## Quality bar

- Every number, date, name, and citation came from the user or is marked as an assumption.
- The artifact can be used without reading this skill again.
- Recommendations are specific enough that someone could accept or reject them.
- Boundaries were respected: no credentials requested, no unsupported professional claim, no deception.

## Example

### Scenario

Mara Chen, founder at Northline Studio in Calgary, needs a decision record by 30 September 2026. A leadership team chose to pause a second product line after a renewal slipped, and they want the reason written down.

### Example data

```text
From: Mara Chen, founder
Organization: Northline Studio, Calgary
Date: 14 September 2026
Needed by: 30 September 2026

A leadership team chose to pause a second product line after a renewal slipped, and they want the reason written down.

The decision in one sentence: A leadership team chose to pause a second product line after a renewal slipped, and they want the reason written down
Alternatives considered: two deals cited from memory. Neither has a written loss reason
Facts used: Bright Axle and one other, both unconfirmed as of 14 September 2026
Who decided and when: 30 September 2026
```

### Example outcome

**Decision record**
To: Mara Chen, founder, Northline Studio
Date: 14 September 2026 · Needed by: 30 September 2026

**Decision**
Drove it, and the condition that would reopen it.

**What the file supports**

| Input | Value | Status |
| --- | --- | --- |
| The decision in one sentence | A leadership team chose to pause a second product line after a renewal slipped, and they want the reason written down | Needs confirmation |
| Alternatives considered | two deals cited from memory. Neither has a written loss reason | Carried into the draft |
| Facts used | Bright Axle and one other, both unconfirmed as of 14 September 2026 | Carried into the draft |
| Who decided and when | 30 September 2026 | Needs confirmation |

**How this draft was built**

**1. State the decision**  
One sentence, past or present tense, with the date and the decider. No preamble.

**2. Record alternatives**  
At least one real alternative that was rejected, and why. If none was considered, say that plainly.

**3. Cite facts**  
List only evidence the user provided. Do not backfill a rationale that sounds smarter than the actual one.

**4. Name the reopen condition**  
What new fact would justify revisiting the decision. Decisions without reopen conditions become dogma.

**5. Note consequences**  
Who must change what by when because of this decision.

**Deliberately not done**
- Rewriting history to make a messy decision look inevitable.
- Logging every tiny choice.
- Omitting the rejected alternative.

**Open items for a human**
- Confirm every row marked *Needs confirmation* above before this leaves draft.
- Anything absent from the file stayed absent. No figure, date, or name was supplied from outside it.

Next: Mara Chen by 30 September 2026. This is a draft, not a sign-off.

## Anti-patterns

- Rewriting history to make a messy decision look inevitable.
- Logging every tiny choice.
- Omitting the rejected alternative.

## Related skills

- `architecture-decision-record`
- `board-memo-writer`
- `founder-decision-review`

Attribution

SYasJSYasJ
View sourceSee grades on GitHubMore from SYasJ →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →