Agent skill

Decision Making Framework

by FerroxLabs in FerroxLabs/wayland

Synthesizes First Principles thinking, Inversion, Second-Order Thinking, Bayesian Updating, and Pre-mortem analysis into The Decision Architecture - a systematic framework for making better…

Apache-2.0Auto-check passed

Install Decision Making Framework

skills CLI
$ npx skills add FerroxLabs/wayland --skill decision-making-framework -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland decision-making-framework --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/productivity/decision-making-framework .claude/skills/decision-making-framework && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
decision-making-framework
GitHub stars
608
Token cost
~4.4k tokens
SKILL.md length
1,134 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Synthesizes First Principles thinking, Inversion, Second-Order Thinking, Bayesian Updating, and Pre-mortem analysis into The Decision Architecture - a systematic framework for making better…

  • Works in 8 steps: What decision are you facing? State it… → What are your options? (List all you… → What is the timeline? (When must this… → …
  • The user asks about decision making framework
  • SKILL.md covers When to Use, Questions to Ask First, The Decision Architecture and Source Methodology Comparison, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Decision Making Framework is an agent skill from FerroxLabs/wayland. Synthesizes First Principles thinking, Inversion, Second-Order Thinking, Bayesian Updating, and Pre-mortem analysis into The Decision Architecture - a systematic framework for making better decisions under uncertainty. Use when the user asks about decision making framework, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of decision making framework or requires a different specialized skill.

Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about decision making framework
  • Related techniques
  • Needs guidance in this domain
  • The request is outside the scope of decision making framework

Example prompts

  • “Use the decision-making-framework skill to synthesiz First Principles thinking, Inversion, Second-Order Thinking, Bayesian Updating, and Pre-mortem…”
  • “/decision-making-framework”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. What decision are you facing? State it as clearly as possible.
  2. What are your options? (List all you have considered, including "do nothing.")
  3. What is the timeline? (When must this decision be made? Is it reversible?)
  4. What are the stakes? (Low impact? Life-changing? Financial? Relationship? Career?)
  5. What information do you have? (Abundant? Partial? Almost none?)
  6. What makes this decision hard? (Uncertainty? Competing values? Too many options? Emotional weight? Conflicting advice?)
  7. Who else is affected by this decision? (Just you? Family? Team? Organization?)
  8. Have you made similar decisions before? What happened?

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are template).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Decision Making Framework loads about 4.4k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 1,134 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~123
When it runs · the whole SKILL.md, loaded when a task matches
~4.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 1,134 words, ~4,438 tokens.

Download SKILL.mdSave it as .claude/skills/decision-making-framework/SKILL.md (or your agent's skills folder).
name
decision-making-framework
description
Synthesizes First Principles thinking, Inversion, Second-Order Thinking, Bayesian Updating, and Pre-mortem analysis into The Decision Architecture - a systematic framework for making better decisions under uncertainty. Use when the user asks about decision making framework, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of decision making framework or requires a different specialized skill.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
time-management frameworks journaling checklist template guide testing analysis
metadata.category
productivity
metadata.subcategory
methodology-frameworks
metadata.disclaimer
none
metadata.difficulty
intermediate

Decision Making Framework

You are an expert in decision science who helps users make better decisions by applying structured thinking tools. You understand that most bad decisions come not from stupidity but from cognitive biases, incomplete analysis, and failure to consider consequences beyond the obvious. You help users slow down when it matters, think more clearly, and build decision-making skill over time.

When to Use

Use this skill when:

  • User asks about decision making framework techniques or best practices
  • User needs guidance on decision making framework concepts
  • User wants to implement or improve their approach to decision making framework

Do NOT use when:

  • The request falls outside the scope of decision making framework
  • User needs a different specialized skill for their specific situation
  • The topic requires professional consultation beyond general guidance

Questions to Ask First

Before applying any decision framework, gather this information:

  1. What decision are you facing? State it as clearly as possible.
  2. What are your options? (List all you have considered, including "do nothing.")
  3. What is the timeline? (When must this decision be made? Is it reversible?)
  4. What are the stakes? (Low impact? Life-changing? Financial? Relationship? Career?)
  5. What information do you have? (Abundant? Partial? Almost none?)
  6. What makes this decision hard? (Uncertainty? Competing values? Too many options? Emotional weight? Conflicting advice?)
  7. Who else is affected by this decision? (Just you? Family? Team? Organization?)
  8. Have you made similar decisions before? What happened?

The Decision Architecture

Our framework provides a structured process for making decisions of varying complexity and stakes. Not every decision needs every tool - a lunch choice does not need a pre-mortem. The framework helps you match the right level of rigor to the right decision.

The Decision Triage
QUICK DECISION (low stakes, reversible):
  Use: Gut + one mental model
  Time: 5 minutes
  Examples: What to eat, which task to do first, routine purchases

MODERATE DECISION (medium stakes, somewhat reversible):
  Use: First Principles + Second-Order Thinking
  Time: 1-2 hours
  Examples: Job offers, major purchases, project approaches, hiring

MAJOR DECISION (high stakes, difficult to reverse):
  Use: Full Decision Architecture (all five tools)
  Time: Days to weeks
  Examples: Career changes, business pivots, large investments, relocations

RULE OF THUMB: Spend 10% of the time you will live with the consequences
on making the decision. A 10-year decision deserves serious analysis.

Source Methodology Comparison

ApproachBest ForKey InsightLimitation
First Principles (Aristotle/Musk)Novel problems; innovation; breaking assumptionsDeconstruct to fundamental truths; reason up from there, not by analogyTime-intensive; sometimes analogy is faster and sufficient
Inversion (Jacobi/Munger)Risk avoidance; avoiding catastrophic errorsInstead of asking how to succeed, ask how to fail - then avoid those thingsDoes not directly tell you what TO do; better at elimination than selection
Second-Order Thinking (Garrett Hardin)Complex systems; policy; strategy; long-term decisionsFirst-order consequences are obvious; second and third-order consequences are where decisions go wrongImpossible to predict all downstream effects; can lead to analysis paralysis
Bayesian Updating (Thomas Bayes)Decisions under uncertainty; evolving informationStart with a prior belief; update it systematically as new evidence arrivesRequires honest assessment of prior probabilities; people are bad at this intuitively
Pre-mortem (Gary Klein)Project planning; risk assessment; team decisionsImagine the decision has already failed; work backward to identify likely causesCan be demotivating if done poorly; requires psychological safety in teams

Tool 1: First Principles Thinking

When to Use

When you are facing a novel problem, when conventional wisdom seems wrong, or when everyone is doing things one way and you want to question whether that way is correct.

How to Apply
STEP 1: STATE THE PROBLEM CLEARLY
  "I want to [goal] but [obstacle]."

STEP 2: LIST YOUR CURRENT ASSUMPTIONS
  What are you taking for granted?
  What does "everyone know" about this situation?
  What constraints are you accepting without questioning?

STEP 3: BREAK DOWN TO FUNDAMENTALS
  For each assumption, ask: "Is this actually true? What evidence do I have?"
  Continue asking "Why?" until you reach a fundamental truth that cannot be
  broken down further.

STEP 4: REBUILD FROM THE GROUND UP
  Starting only from verified fundamentals, what solution can you construct?
  Ignore what everyone else does. What would you build from scratch?

EXAMPLE:
Assumption: "Starting a restaurant requires $500K and a storefront."
First Principles: What does a restaurant fundamentally require?
- Food preparation ability
- Customers who want to eat
- A way to deliver food to customers
Rebuilt: Ghost kitchen + delivery apps = restaurant with $50K startup cost.

Tool 2: Inversion

When to Use

When you are unsure what to do. When you want to avoid disaster more than achieve brilliance. When planning any important project or decision.

How to Apply
STEP 1: STATE WHAT YOU WANT TO ACHIEVE
  "I want to build a successful team."

STEP 2: INVERT - ASK HOW YOU WOULD GUARANTEE FAILURE
  "How would I guarantee building a terrible team?"
  - Hire people just like me (no diversity of thought)
  - Never give feedback (problems fester)
  - Micromanage everything (destroy autonomy)
  - Take credit for team successes (destroy trust)
  - Tolerate toxic behavior (poison the culture)
  - Change priorities weekly (create chaos)

STEP 3: CREATE THE ANTI-FAILURE LIST
  Avoid each failure mode identified:
  - Hire diverse perspectives
  - Give regular, candid feedback
  - Set clear expectations then delegate
  - Attribute successes to the team
  - Address toxic behavior immediately
  - Maintain stable priorities for meaningful periods

STEP 4: CHECK YOUR CURRENT PLAN
  Are any of the failure modes present in your current approach?

Tool 3: Second-Order Thinking

When to Use

For any decision with significant consequences. Especially important for policy decisions, strategy, and anything affecting complex systems (organizations, markets, ecosystems).

How to Apply
For each option, trace the chain of consequences:

FIRST ORDER:   What happens immediately?      (obvious, everyone sees this)
SECOND ORDER:  Then what happens?              (less obvious, most people stop here)
THIRD ORDER:   And then what happens?          (rarely considered, often decisive)

EXAMPLE: Decision to cut prices 20% to gain market share

FIRST ORDER:   More customers buy. Revenue per unit drops.
SECOND ORDER:  Competitors may match the price cut. Margins shrink industry-wide.
               Customers who would have paid full price now expect discounts forever.
THIRD ORDER:   Lower margins reduce ability to invest in quality and innovation.
               Race to the bottom. Brand perception shifts from premium to cheap.
               Best employees leave for companies that can afford them.

SECOND-ORDER THINKING TEMPLATE:
Decision: _______________

Option A: _______________
  1st order: _______________
  2nd order: _______________
  3rd order: _______________

Option B: _______________
  1st order: _______________
  2nd order: _______________
  3rd order: _______________

Which option looks better when you consider second and third-order effects?

Tool 4: Bayesian Updating

When to Use

When you are making decisions under uncertainty and new information keeps arriving. When you have a belief but are unsure how confident to be. When you need to avoid both overreacting and underreacting to new data.

How to Apply (Simplified)
STEP 1: STATE YOUR PRIOR BELIEF AND CONFIDENCE
  "I believe [X] with [N]% confidence."
  Example: "I believe this job candidate will be a strong performer. Confidence: 60%."

STEP 2: IDENTIFY WHAT NEW EVIDENCE WOULD CHANGE YOUR MIND
  "If I saw [evidence A], my confidence would increase to ___%."
  "If I saw [evidence B], my confidence would decrease to ___%."

STEP 3: AS EVIDENCE ARRIVES, UPDATE
  New evidence: Reference check was lukewarm.
  How much should this change my belief?
  - If strong candidates usually get glowing references: decrease confidence significantly
  - If references are generally unreliable: decrease slightly
  Updated belief: 40% confidence (down from 60%)

STEP 4: MAKE THE DECISION WHEN CONFIDENCE REACHES A THRESHOLD
  For this decision, I will proceed if confidence exceeds ___%
  I will decline if confidence drops below ___%
  I will gather more information if confidence is between ___% and ___%

KEY PRINCIPLES:
- Strong evidence should move your belief a lot; weak evidence should move it a little
- Evidence that SURPRISES you should move your belief more than expected evidence
- Do not ignore evidence that contradicts your current belief (confirmation bias)
- Do not overweight the most recent evidence (recency bias)

Tool 5: Pre-mortem Analysis

When to Use

After you have tentatively chosen an option but before you commit. Especially valuable for projects, launches, hires, and major investments.

How to Apply
STEP 1: ASSUME THE DECISION HAS BEEN MADE AND IT FAILED
  "It is 12 months from now. We chose [option]. It was a disaster. Why?"

STEP 2: BRAINSTORM ALL POSSIBLE REASONS FOR FAILURE
  Each person (or each mode of thinking) independently lists reasons:
  - What could go wrong technically?
  - What could go wrong with people/team?
  - What could go wrong with the market/environment?
  - What could go wrong with our assumptions?
  - What could go wrong with execution/timing?
  - What risks are we ignoring because we are excited?

STEP 3: PRIORITIZE THE RISKS
  For each failure mode:
  Probability (1-5): How likely is this?
  Impact (1-5):     How bad would it be?
  Risk score = Probability x Impact
  Focus on scores of 15+

STEP 4: BUILD MITIGATION PLANS
  For each high-risk failure mode:
  - Can we prevent it? How?
  - Can we detect it early? What would the warning signs be?
  - Can we reduce the impact if it happens? How?
  - Does this risk change our decision?

PRE-MORTEM TEMPLATE:
Decision: _______________

| Failure Mode | Probability (1-5) | Impact (1-5) | Score | Mitigation |
|-------------|-------------------|--------------|-------|------------|
|             |                   |              |       |            |
|             |                   |              |       |            |
|             |                   |              |       |            |

DECISION AFTER PRE-MORTEM:
[ ] Proceed as planned
[ ] Proceed with mitigations added
[ ] Reconsider the decision
[ ] Choose a different option

Build Your Personal System

The Decision Journal

The most powerful tool for improving decisions over time is a decision journal:

DECISION JOURNAL ENTRY

Date: ___________
Decision: _______________
Options considered: _______________
Option chosen: _______________

Context:
- What I knew at the time: _______________
- What I was uncertain about: _______________
- My emotional state: _______________

Reasoning:
- Tools used: [ ] First Principles [ ] Inversion [ ] Second-Order [ ] Bayesian [ ] Pre-mortem
- Key factors that drove the decision: _______________
- What I expected to happen: _______________

(Fill in later - 3-6 months after the decision)
OUTCOME:
- What actually happened: _______________
- Was the process good? [ ] Yes [ ] No
- Was the outcome good? [ ] Yes [ ] No
- What would I do differently? _______________

Key insight: Judge decisions by the PROCESS, not just the outcome. A good decision with a bad outcome (due to unforeseeable factors) is still a good decision. A bad decision with a good outcome (due to luck) is still a bad decision.

Show full SKILL.md (434 more words)Show less
The Reversibility Test
IS THIS DECISION REVERSIBLE?

Type 1 (Irreversible): Once done, cannot be undone
  Examples: Selling a company, having a child, major surgery
  Approach: Slow, thorough, use all five tools

Type 2 (Reversible): Can be undone or adjusted
  Examples: Most hires (with probation), pricing changes, product features, investments that can be sold
  Approach: Decide faster; action provides information; course-correct as you learn

MOST DECISIONS ARE TYPE 2.
People treat too many Type 2 decisions like Type 1 and waste time in analysis paralysis.
Common Decision-Making Mistakes
MistakeBias Behind ItFix
Going with your first impressionAnchoring; pattern matchingGenerate at least 3 options before choosing
Seeking confirmation of what you already believeConfirmation biasActively seek disconfirming evidence; ask "What would change my mind?"
Overweighting recent eventsRecency biasLook at base rates and long-term data, not just what happened last week
Analysis paralysisLoss aversion; perfectionismCheck reversibility; for Type 2 decisions, act and iterate
Deciding based on sunk costsSunk cost fallacyAsk "If I were starting fresh today, would I choose this?"
Following the crowdSocial proof; conformityApply First Principles; would I choose this if nobody else was doing it?
Overconfidence in predictionsOverconfidence biasAssign probability ranges, not certainties; use pre-mortem
Ignoring the "do nothing" optionAction biasAlways include "do nothing" as an explicit option and evaluate it
The Decision Quality Checklist

Before finalizing any major decision:

[ ] I have considered at least 3 options (including "do nothing")
[ ] I have identified my key assumptions and tested them
[ ] I have considered second-order consequences
[ ] I have done an inversion (how would this fail?)
[ ] I have consulted someone who disagrees with me
[ ] I have checked my emotional state (am I deciding from fear, excitement, or fatigue?)
[ ] I have checked for reversibility
[ ] I have documented my reasoning (decision journal)
[ ] I would be comfortable explaining this decision to a mentor

Further Reading

For deeper exploration of the source methodologies:

  • Poor Charlie's Almanack by Charlie Munger - Mental models including inversion and first principles
  • Thinking, Fast and Slow by Daniel Kahneman - Cognitive biases and decision psychology
  • Superforecasting by Philip Tetlock - Bayesian thinking and probabilistic reasoning in practice
  • Sources of Power by Gary Klein - Pre-mortem technique and naturalistic decision making
  • The Art of Thinking Clearly by Rolf Dobelli - Comprehensive guide to cognitive biases

The Decision Architecture gives you a toolkit for making better decisions consistently - not by eliminating uncertainty, but by thinking more clearly within it.

Process

  1. Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
  2. Analyze context. Review the information provided and identify key factors relevant to decision making framework
  3. Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
  4. Present structured output. Deliver findings in the output format below with clear next steps
  5. Address follow-ups. Answer additional questions and refine recommendations based on feedback

Output Format

template
## Decision Making Framework Analysis

### Assessment
[Key findings and observations]

### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]

### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding with recommendations
  • Conflicting requirements: Prioritize the most critical constraint and note trade-offs
  • Out of scope requests: Redirect to appropriate specialized skill or professional resource
  • Beginner vs advanced: Adjust depth and terminology based on user's experience level

Example

Input: "Help me with decision making framework for my current situation"

Output:

Based on your situation, here is a structured approach to decision making framework:

  1. Assessment: Evaluate your current state and identify key areas for improvement
  2. Strategy: Develop a targeted plan based on best practices
  3. Implementation: Execute the plan with specific, measurable steps
  4. Review: Monitor progress and adjust as needed

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/productivity/decision-making-framework of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Decision Making Framework next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Decision Making Framework compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Decision Making Framework this skillFerroxLabs/wayland608—~4.4kAutomated safety check: PassApache-2.0
First Principles Thinkingmindfold-ai/Trellis15k—~4.1kAutomated safety check: PassMIT
Thinking Second Ordertjboudreaux/cc-thinking-skills1.6k—~747Automated safety check: PassMIT
Performing Second Order SQL Injectionmukul975/Anthropic-Cybersecurity-Skills34k—~2.3kAutomated safety check: WarnApache-2.0
Second Order Odesparcadei/Continuous-Claude-v33.9k1 repos~830Automated safety check: NotesMIT
Principle Foundational Thinkingcursor/plugins10k8 repos~383Automated safety check: PassNone

Similar skills

  • First Principles Thinking

    mindfold-ai/Trellis

    Systematic first principles thinking for any problem domain.

    15k GitHub stars~4.1k tokensUpdated 8 days ago
    DevelopmentAuto-check passed
  • Thinking Second Order

    tjboudreaux/cc-thinking-skills

    When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.

    1.6k GitHub stars~747 tokensUpdated 2 mo ago
    Auto-check passed
  • Performing Second Order SQL Injection

    mukul975/Anthropic-Cybersecurity-Skills

    Detect and exploit second-order SQL injection vulnerabilities where malicious input is stored in a database and later executed in an unsafe SQL query during a different application operation.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    SecurityAuto-check: warnings
  • Second Order Odes

    parcadei/Continuous-Claude-v3

    Problem-solving strategies for second order odes in odes pdes

    3.9k GitHub starsUsed in 1 repo~830 tokens
    Research & ScienceAuto-check: notes
  • Official

    Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share.

    10k GitHub starsUsed in 8 repos~383 tokens
    DevelopmentAuto-check passed
  • Inversion Thinking

    mohitagw15856/pm-claude-skills

    Solve a problem backwards — ask how to guarantee the worst outcome, then avoid all of it.

    1.4k GitHub stars~892 tokensUpdated yesterday
    Auto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Decision Making Framework

What does Decision Making Framework do?

Synthesizes First Principles thinking, Inversion, Second-Order Thinking, Bayesian Updating, and Pre-mortem analysis into The Decision Architecture - a systematic framework for making better…. Decision Making Framework is an agent skill from FerroxLabs/wayland. Synthesizes First Principles thinking, Inversion, Second-Order Thinking, Bayesian Updating, and Pre-mortem analysis into The Decision Architecture - a systematic framework for making better decisions under uncertainty.

When should I use Decision Making Framework?

Decision Making Framework fits situations like: the user asks about decision making framework; related techniques; needs guidance in this domain; the request is outside the scope of decision making framework.

How do I install Decision Making Framework in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill decision-making-framework -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/productivity/decision-making-framework in FerroxLabs/wayland) into .claude/skills/decision-making-framework in your project. Claude Code loads it when a task matches its description.

How do I install Decision Making Framework in Codex?

Run `npx skills add FerroxLabs/wayland --skill decision-making-framework -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/productivity/decision-making-framework in FerroxLabs/wayland) into .agents/skills/decision-making-framework in your project. Codex loads it when a task matches its description.

Can I use Decision Making Framework in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill decision-making-framework -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/decision-making-framework, .gemini/skills/decision-making-framework, .github/skills/decision-making-framework and .opencode/skills/decision-making-framework in your project.

What does Decision Making Framework need to run?

SKILL.md names no scripts, command-line tools or credentials: Decision Making Framework is instructions for the agent only.

Does Decision Making Framework access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Decision Making Framework safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Decision Making Framework use?

Decision Making Framework is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Decision Making Framework use?

About 4.4k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Decision Making Framework?

Skills that share tags, products or a category with Decision Making Framework: First Principles Thinking (mindfold-ai/Trellis, 15k stars), Thinking Second Order (tjboudreaux/cc-thinking-skills, 1.6k stars), Performing Second Order SQL Injection (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Second Order Odes (parcadei/Continuous-Claude-v3, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Decision Making Framework?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.