023-assumption-analysis — Claude Code skill for assumption analysis
023-assumption-analysis is a skill that identifies and ranks assumptions and unknowns in a framed problem before design, then outlines validation checks.
Apache-2.0 140 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 023-assumption-analysis -a claude-codeWhat 023-assumption-analysis does
Use it after a problem has been framed and its root causes explored. The skill separates claims believed to be true but not yet checked from facts that remain unknown, then ranks both by impact and confidence.
It produces an assumptions list, an unknowns list, and a validation plan that says how and when to check high-impact items with low confidence. Before applying the guidance, the agent must read references/023-assumption-analysis.md. When the problem description is too vague, the skill calls for clarification instead of inventing assumptions or tests.
What it helps with
- surface hidden beliefs in a problem frame
- separate unverified claims from unknown facts
- rank risks by impact and confidence
- plan checks for high-risk items
- draft an Assumption Analysis section for a Functional Specification
Example prompts for the agent
- Before design starts, identify the assumptions and unknowns in this problem.
- Rank each item by impact and confidence, then propose how and when to validate it.
- Draft an Assumption Analysis section for this Functional Specification.
How to install 023-assumption-analysis
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 023-assumption-analysis -a claude-code2Manually: put the files in place
~/.claude/skills/023-assumption-analysis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/023-assumption-analysis/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 023-assumption-analysis -a codex2Manually: put the files in place
.agents/skills/023-assumption-analysis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 023-assumption-analysis -a cursor2Manually: put the files in place
.cursor/skills/023-assumption-analysis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/023-assumption-analysis2Manually: put the files in place
.github/skills/023-assumption-analysis/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 023-assumption-analysis -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/023-assumption-analysisManually: put the files in place
.devin/skills/023-assumption-analysis/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 023-assumption-analysis -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 023-assumption-analysis
How do I install 023-assumption-analysis in Claude Code?
Run npx skills add jabrena/plinth --skill 023-assumption-analysis -a claude-code. The skill file is at ~/.claude/skills/023-assumption-analysis/SKILL.md.
What does 023-assumption-analysis do?
It identifies assumptions and unknowns in an explored problem, ranks them by impact and confidence, and prepares a plan to validate them.
What happens when the problem description is vague?
The skill should flag the need for clarification rather than inventing assumptions, unknowns, or validation steps.
Source text
SKILL.md · Apache-2.0
--- 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 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 ## 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. 2. **Surface Explicit Assumptions** State each assumption as a falsifiable claim believed true but not yet verified. 3. **List Unknowns** List facts that are not yet known either way, distinct from assumptions. 4. **Rank by Impact and Confidence** Rank assumptions and unknowns by impact if wrong and by current confidence, prioritizing high-impact, low-confidence items. 5. **Define the Validation Plan** Name how and when each high-priority assumption or unknown will be validated. 6. **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](references/023-assumption-analysis.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth