023-assumption-analysis
Skill452 starsChanged 3 months agoApache-2.0View on GitHub
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
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
MUST: read references/023-assumption-analysis.md before applying Assumption Analysis guidance
- Very specific: line 44
Read references/023-assumption-analysis.md, then review the problem frame and root-cause findings for implicit beliefs.
≈ “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.
Files
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-mappingand 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.mdbefore 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
- Read the Reference
Read references/023-assumption-analysis.md, then review the problem frame and root-cause findings for implicit beliefs.
- Surface Explicit Assumptions
State each assumption as a falsifiable claim believed true but not yet verified.
- List Unknowns
List facts that are not yet known either way, distinct from assumptions.
- Rank by Impact and Confidence
Rank assumptions and unknowns by impact if wrong and by current confidence, prioritizing high-impact, low-confidence items.
- Define the Validation Plan
Name how and when each high-priority assumption or unknown will be validated.
- 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.
Other versions1 project uses a version of this.
Word for word · 1
- jabrena/plinth★ 448100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository124 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 001-commands-inventorySkill
- 002-agents-inventorySkill
- 003-skills-inventorySkill
- 004-commands-installationSkill
- 005-agents-installationSkill
- 012-agile-epicSkill
- 013-agile-featureSkill
- 014-agile-user-storySkill
- 021-problem-framingSkill
- 022-root-cause-analysisSkill
- 024-context-mappingSkill
- 025-quality-attribute-discoverySkill
- 030-architecture-adr-generalSkill
- 033-architecture-diagramsSkill
- 041-planning-plan-modeSkill
- 042-planning-openspecSkill
- 043-planning-github-issuesSkill
- 044-planning-jiraSkill
- 045-planning-azure-devopsSkill
- 051-design-two-steps-methodsSkill
- 052-design-hamburger-methodSkill
- 053-design-simple-rulesSkill
- 054-design-tddSkill
- 055-design-parallel-changeSkill
- 056-design-avoid-breaking-changesSkill
- 057-design-feature-togglesSkill
- 058-design-bddSkill
- 059-design-atddSkill
- 110-java-maven-best-practicesSkill
- 111-java-maven-dependenciesSkill
- 112-java-maven-pluginsSkill
- 113-java-maven-documentationSkill
- 114-java-maven-searchSkill
- 121-java-object-oriented-designSkill
- 122-java-type-designSkill
- 123-java-design-patternsSkill
- 124-java-secure-codingSkill
- 125-java-concurrencySkill
- 126-java-exception-handlingSkill
- 128-java-genericsSkill
- 130-java-testing-strategiesSkill
- 131-java-testing-unit-testingSkill
- 132-java-testing-integration-testingSkill
- 133-java-testing-acceptance-testsSkill
- 141-java-refactoring-with-modern-featuresSkill
- 142-java-functional-programmingSkill
- 143-java-functional-exception-handlingSkill
- 144-java-data-oriented-programmingSkill
- 145-java-refactoring-high-performanceSkill
- 151-java-performance-jmeterSkill
- 152-java-performance-gatlingSkill
- 161-java-profiling-detectSkill
- 162-java-profiling-analyzeSkill
- 163-java-profiling-refactorSkill
- 164-java-profiling-verifySkill
- 170-java-documentationSkill
- 181-java-observability-loggingSkill
- 182-java-observability-metrics-micrometerSkill
- 183-java-observability-tracing-opentelemetrySkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

