agentleFS
Sign inStart free
paultyngpaultyng/skill-issue/skills/create-decision-document/SKILL.md

create-decision-document

Skill8 starsChanged 3 months agoMITView on GitHub

Create or update a Notion decision document with a structured options/pros/cons/recommendation template. Use when the user asks to create a decision doc, design doc, evaluation doc, or comparison in Notion.

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create or update a decision document in Notion using the Notion MCP.

    line 8
  2. Distinctive:

    If the user asks for research before writing:

    line 19
  3. Distinctive:

    Use Sourcegraph for organization's codebase patterns and precedent

    line 20
  4. Distinctive:

    Use web search for external APIs, standards, and vendor comparisons

    line 21
  5. Distinctive:

    Use Notion for existing internal docs and prior decisions

    line 22
  6. Distinctive:

    Use the Notion MCP to create a page with this structure:

    line 27
  7. Distinctive:

    Do not prefix Pros/Cons items with "Good:" or "Bad:".

    line 59
  8. Distinctive:

    If there are criteria or requirements, use a comparison table rather than repeating them per option.

    line 61
  9. Distinctive:

    Update the recommendation after discussion

    line 67
  10. Distinctive:

    Add a "Decision" or "Status" field marking the choice as final

    line 68

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create Decision Document

Create or update a decision document in Notion using the Notion MCP.

1. Gather Context

Determine from the user:

  • Title: what decision is being made
  • Location: which Notion page or database to create under (ask if unclear)
  • Options: the alternatives being evaluated (may emerge during research)

2. Research (if needed)

If the user asks for research before writing:

  • Use Sourcegraph for organization's codebase patterns and precedent
  • Use web search for external APIs, standards, and vendor comparisons
  • Use Notion for existing internal docs and prior decisions
  • Be terse in research summaries

3. Create the Document

Use the Notion MCP to create a page with this structure:

# <Decision Title>

## Problem Statement
<1-2 sentences describing what needs to be decided and why>

## Options

### Option A: <Name>
**Pros**
- <terse bullet>
- <terse bullet>

**Cons**
- <terse bullet>
- <terse bullet>

### Option B: <Name>
**Pros**
- <terse bullet>

**Cons**
- <terse bullet>

## Recommendation
<Which option and why, 1-2 sentences>

Formatting rules:

  • Be terse throughout. No filler.
  • Do not prefix Pros/Cons items with "Good:" or "Bad:".
  • Bullet points, not prose paragraphs.
  • If there are criteria or requirements, use a comparison table rather than repeating them per option.

4. Follow-up

Common follow-up actions (do only if asked):

  • Link a PR to the decision doc
  • Update the recommendation after discussion
  • Add a "Decision" or "Status" field marking the choice as final

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free