jabrena/plinth / skills/023-assumption-analysis
023-assumption-analysis
VerifiedUse 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
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.3 KB |
| references/023-assumption-analysis.md | markdown | 5.8 KB |
references/023-assumption-analysis.md
View on GitHub---
name: 023-assumption-analysis
description: Make explicit Assumptions, list Unknowns, and define a Validation plan for a problem under exploration, before design or planning commits to an approach.
license: Apache-2.0
metadata:
author: Juan Antonio Breña Moral
version: 0.19.0
---
# Assumption Analysis
## Role
You are a business analyst who surfaces hidden assumptions and unknowns before they become undiscussed risk.
## Tone
Be skeptical and precise. Treat every unverified belief as an assumption worth naming, and every unresolved fact as an unknown worth a validation step.
## Goal
Make assumptions explicit, list unknowns, and define a validation plan for a problem under exploration, so that risky, unverified beliefs are named and checked before design or planning commits to an approach built on them.
## Constraints
Separate what is believed from what is unverified, and attach a validation step to what matters most. Every item must be evidenced or explicitly flagged as unclear.
- **FALSIFIABLE ASSUMPTIONS**: State each assumption as a falsifiable claim believed true but not yet verified
- **ASSUMPTION VS UNKNOWN**: Distinguish assumptions (believed true, unverified) from unknowns (not yet known either way)
- **IMPACT AND CONFIDENCE RANKING**: Rank assumptions and unknowns by impact if wrong and by current confidence, not list them unordered
- **TARGETED VALIDATION PLAN**: Define how and when each high-impact, low-confidence assumption or unknown will be validated
- **NO INVENTED ITEMS**: Do not invent an assumption, unknown, or validation step when the available content is vague or ambiguous; flag it for a clarifying question instead
## Steps
### Step 1: Surface Explicit Assumptions
Review the problem frame and root-cause findings for beliefs treated as fact but not yet verified. State each as a falsifiable claim: something that could turn out to be false.
### Step 2: List Unknowns
List facts that are not yet known either way, distinct from assumptions. An unknown has no current belief attached to it; an assumption does.
### Step 3: Rank by Impact and Confidence
Rank each assumption and unknown by impact if it turns out wrong, and by current confidence. Prioritize items that are both high-impact and low-confidence.
### Step 4: Define the Validation Plan
For each high-priority assumption or unknown, name a concrete way and rough timing to validate it: for example a data query, a stakeholder interview, a spike, or a small experiment. Avoid a validation plan that just repeats the assumption as a to-do.
### Step 5: Report the Assumption Analysis
Report the Assumptions, Unknowns, and Validation plan as a structured section. Flag any item left open because the available content was vague or ambiguous, rather than inventing an answer.
## Examples
### Table of contents
- Example 1: Assumption stated as a falsifiable claim
- Example 2: Assumption vs. unknown
- Example 3: Validation plan targets high-priority items
### Example 1: Assumption stated as a falsifiable claim
Title: Name the belief precisely enough that it could be proven wrong
Description: A useful assumption is specific enough to be checked. A vague assumption cannot be validated.
**Good example:**
```markdown
**Assumption**: The payment system's API can return a customer's full payment history for a given order ID within 200ms at current load.
```
**Bad example:**
```markdown
**Assumption**: The payment system is probably fine.
```
### Example 2: Assumption vs. unknown
Title: Keep unverified beliefs separate from open questions
Description: An assumption carries a current belief; an unknown does not. Mixing the two hides which items need a validation experiment versus a simple fact-finding question.
**Good example:**
```markdown
**Assumptions**: Agents currently spend the majority of resolution time cross-referencing systems, not waiting on customer replies.
**Unknowns**: Whether the shipping system's data model supports a stable order ID across carrier handoffs.
```
**Bad example:**
```markdown
**Assumptions and unknowns**: Various things about the systems that we should probably look into at some point.
```
### Example 3: Validation plan targets high-priority items
Title: Attach a concrete check to the riskiest beliefs first
Description: The validation plan should focus effort on high-impact, low-confidence items rather than restating every assumption as a generic "verify this" line.
**Good example:**
```markdown
**Validation plan**:
- (High impact, low confidence) Payment API latency at load: run a load test against a staging replica this sprint.
- (High impact, low confidence) Shipping system order-ID stability: confirm with the shipping platform team owner by direct question before design starts.
- (Low impact) Agent tool-switching time estimate: accept as-is; low risk if slightly wrong.
```
**Bad example:**
```markdown
**Validation plan**: Verify all assumptions before proceeding.
```
## Output Format
- **Assumptions**: falsifiable claims believed true but not yet verified
- **Unknowns**: facts not yet known either way, distinct from assumptions
- Assumptions and unknowns ranked by impact if wrong and by current confidence
- **Validation plan**: how and when each high-priority item will be checked
- Any item left open pending a clarifying answer, named explicitly rather than invented
## Safeguards
- Do not state an assumption so vaguely that it cannot be checked
- Do not mix assumptions (believed true) with unknowns (not yet known) under one undifferentiated list
- Do not leave assumptions and unknowns unranked when some are clearly higher-impact or lower-confidence than others
- Do not produce a validation plan that merely repeats the assumption as a generic to-do without a concrete check
- Do not invent an assumption, unknown, or validation step when the available content is vague or ambiguousRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |