Agent skill

023 Assumption Analysis

by jabrena in jabrena/plinth

A skill your agent uses when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan.

Apache-2.0Auto-check passed

Install 023 Assumption Analysis

skills CLI
$ npx skills add jabrena/plinth --skill 023-assumption-analysis -a claude-code

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

GitHub CLI
$ gh skill install jabrena/plinth 023-assumption-analysis --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/jabrena/plinth.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/023-assumption-analysis .claude/skills/023-assumption-analysis && 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
023-assumption-analysis
GitHub stars
447
Token cost
~835 tokens
SKILL.md length
373 words
Files
2 (incl. references)
Skills in repo
124
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan.

  • A framed and root-caused problem needs its assumptions made explicit before design
  • SKILL.md covers Constraints, When to use this skill, Workflow and Reference
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Planning begins — explicit Assumptions

What it does

023 Assumption Analysis is an agent skill from jabrena/plinth. Use when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan. This should trigger when an issue's Assumption Analysis point of view needs evaluation, or when a maintainer directly asks to surface hidden assumptions and unknowns before committing to an approach. Part of Plinth Toolkit

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/023-assumption-analysis.md`).

The repository describes itself as: Plinth is an AI-native engineering toolkit for modern Java enterprise SDLC, built around reusable Commands, Agents, Skills, and MCP Servers. The licence is Apache-2.0.

When your agent uses it

  • A framed and root-caused problem needs its assumptions made explicit before design
  • Planning begins — explicit Assumptions
  • A Validation plan
  • An issues Assumption Analysis point of view needs evaluation

Example prompts

  • “/023-assumption-analysis”

What it can do on your machine

Read from SKILL.md and the folder at commit dca88dc. 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.

    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

023 Assumption Analysis loads about 835 tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 373 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~835
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

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 jabrena/plinth at commit dca88dc, republished under its Apache-2.0 licence (© jabrena). 373 words, ~835 tokens.

Download SKILL.mdSave it as .claude/skills/023-assumption-analysis/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
023-assumption-analysis
description
Use when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan. This should trigger when an issue's Assumption Analysis point of view needs evaluation, or when a maintainer directly asks to surface hidden assumptions and unknowns before committing to an approach. Part of Plinth Toolkit
license
Apache-2.0
metadata.author
Juan Antonio Breña Moral
metadata.version
0.19.0

Assumption Analysis

Guide production of explicit Assumptions, a list of Unknowns, and a Validation plan for a problem under exploration. This is an interactive SKILL.

What is covered in this Skill?

  • Surfacing assumptions implicit in the problem frame and root-cause findings
  • Distinguishing an assumption (believed true, not yet verified) from an unknown (not yet known either way)
  • Ranking assumptions and unknowns by impact and confidence
  • Defining a validation plan that names how and when each risky assumption or unknown will be checked
  • Feeding assumption and unknown findings into 024-context-mapping and the remaining Functional Specification lenses

Constraints

Make assumptions and unknowns explicit before they become undiscussed risk. When this technique is orchestrated by another workflow, the orchestrator owns clarifying-question sequencing; when applied standalone, ask directly.

  • MUST read references/023-assumption-analysis.md before applying Assumption Analysis guidance
  • MUST state each assumption as a falsifiable claim believed true but not yet verified
  • MUST distinguish assumptions (believed true) from unknowns (not yet known either way)
  • MUST rank assumptions and unknowns by impact if wrong and by current confidence
  • MUST define a validation plan naming how and when each high-impact, low-confidence assumption or unknown will be checked
  • MUST NOT invent an assumption, unknown, or validation step when the available content is vague or ambiguous; flag the gap for a clarifying question instead
Show full SKILL.md (159 more words)Show less

When to use this skill

  • Surface the assumptions behind this problem
  • List the unknowns for this issue
  • Build a validation plan for these assumptions
  • Apply assumption analysis before design begins
  • Draft the Assumption Analysis section of a Functional Specification

Workflow

  1. Read the Reference

Read references/023-assumption-analysis.md, then review the problem frame and root-cause findings for implicit beliefs.

  1. Surface Explicit Assumptions

State each assumption as a falsifiable claim believed true but not yet verified.

  1. List Unknowns

List facts that are not yet known either way, distinct from assumptions.

  1. Rank by Impact and Confidence

Rank assumptions and unknowns by impact if wrong and by current confidence, prioritizing high-impact, low-confidence items.

  1. Define the Validation Plan

Name how and when each high-priority assumption or unknown will be validated.

  1. Report the Assumption Analysis

Report the Assumptions, Unknowns, and Validation plan, and flag any item left open pending a clarifying answer.

Reference

For detailed guidance, examples, and constraints, see references/023-assumption-analysis.md.

© jabrena, 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

SKILL.md and 1 other file (references) in skills/023-assumption-analysis of jabrena/plinth.

  • SKILL.md
  • references/023-assumption-analysis.md

Open the folder on GitHubat commit dca88dc

Compare with similar skills

023 Assumption Analysis 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.

023 Assumption Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
023 Assumption Analysis this skilljabrena/plinth447—~835Automated safety check: PassApache-2.0
Monte Carlo Analyze Root Causesickn33/agentic-awesome-skills47k1 repos~4kAutomated safety check: PassApache-2.0
Root Cause Paretodavila7/claude-code-templates33k—~791Automated safety check: PassMIT
Root Cause Debugginggarrytan/gstack136k—~1.4kAutomated safety check: PassMIT
Root Cause Investigationgarrytan/gstack136k—~12kAutomated safety check: NotesMIT
Om Root Causego-musicfox/go-musicfox2.6k1 repos~1.4kAutomated safety check: NotesGPL-3.0

Similar skills

  • Monte Carlo Analyze Root Cause

    sickn33/agentic-awesome-skills

    Curated upstream guidance for Monte Carlo Analyze Root Cause; use when the workflow matches the user goal.

    47k GitHub starsUsed in 1 repo~4k tokens
    DevelopmentAuto-check passed
  • Root Cause Pareto

    davila7/claude-code-templates

    Build a decision-grade Pareto for downtime, defects, complaints or delays - with unit-of-measure discipline, category hygiene, exposure normalization and a follow-up metric.

    33k GitHub stars~791 tokensUpdated today
    DevelopmentAuto-check passed
  • Root Cause Debugging

    garrytan/gstack

    Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.

    136k GitHub stars~1.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.

    136k GitHub stars~12k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Om Root Cause

    go-musicfox/go-musicfox

    Read-only root-cause analysis for a tracker issue. An agent skill from go-musicfox/go-musicfox.

    2.6k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check: notes
  • 5why Root Cause

    hashgraph-online/awesome-codex-plugins

    Drill into root cause with a 5-Why why chain, why analysis, or structured root cause investigation.

    1.3k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed

More from jabrena/plinth

All 124 skills in this repo
  • A skill your agent uses when you need to add or review fuzz testing for Java APIs with CATS — including contract-driven negative testing, malformed payload validation, boundary input exploration, CI…

    447 GitHub stars~874 tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, UML Deployment Diagrams…

    447 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning…

    447 GitHub stars~3.2k tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to set up JMeter performance testing for a Java project — including creating the run-jmeter.sh script from the exact template, configuring load tests with…

    447 GitHub stars~842 tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven…

    447 GitHub stars~903 tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the…

    447 GitHub stars~697 tokensUpdated 3 days ago
    Auto-check passed

Questions about 023 Assumption Analysis

What does 023 Assumption Analysis do?

A skill your agent uses when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan. 023 Assumption Analysis is an agent skill from jabrena/plinth. Use when a framed and root-caused problem needs its assumptions made explicit before design or planning begins — explicit Assumptions, Unknowns, and a Validation plan.

When should I use 023 Assumption Analysis?

023 Assumption Analysis fits situations like: A framed and root-caused problem needs its assumptions made explicit before design; planning begins — explicit Assumptions; A Validation plan; an issues Assumption Analysis point of view needs evaluation.

How do I install 023 Assumption Analysis in Claude Code?

Run `npx skills add jabrena/plinth --skill 023-assumption-analysis -a claude-code`. Or copy the skill folder (skills/023-assumption-analysis in jabrena/plinth) into .claude/skills/023-assumption-analysis in your project. Claude Code loads it when a task matches its description.

How do I install 023 Assumption Analysis in Codex?

Run `npx skills add jabrena/plinth --skill 023-assumption-analysis -a codex`. Or copy the skill folder (skills/023-assumption-analysis in jabrena/plinth) into .agents/skills/023-assumption-analysis in your project. Codex loads it when a task matches its description.

Can I use 023 Assumption Analysis 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 jabrena/plinth --skill 023-assumption-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/023-assumption-analysis, .gemini/skills/023-assumption-analysis, .github/skills/023-assumption-analysis and .opencode/skills/023-assumption-analysis in your project.

What does 023 Assumption Analysis need to run?

SKILL.md names no scripts, command-line tools or credentials: 023 Assumption Analysis is instructions for the agent only.

Does 023 Assumption Analysis 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 023 Assumption Analysis 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 023 Assumption Analysis use?

023 Assumption Analysis 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 023 Assumption Analysis use?

About 835 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to 023 Assumption Analysis?

Skills that share tags, products or a category with 023 Assumption Analysis: Monte Carlo Analyze Root Cause (sickn33/agentic-awesome-skills, 47k stars), Root Cause Pareto (davila7/claude-code-templates, 33k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Root Cause Investigation (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains 023 Assumption Analysis?

jabrena (a GitHub user) maintains it in jabrena/plinth, which has 447 GitHub stars. The repository holds 124 skills in this directory. The repository was last updated on October 7, 2026.

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