jabrena/023-assumption-analysis
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
npx skills add https://github.com/jabrena/plinth --skill 023-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?
024-context-mapping and the remaining Functional Specification lensesMake 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.
references/023-assumption-analysis.md before applying Assumption Analysis guidanceRead references/023-assumption-analysis.md, then review the problem frame and root-cause findings for implicit beliefs.
State each assumption as a falsifiable claim believed true but not yet verified.
List facts that are not yet known either way, distinct from assumptions.
Rank assumptions and unknowns by impact if wrong and by current confidence, prioritizing high-impact, low-confidence items.
Name how and when each high-priority assumption or unknown will be validated.
Report the Assumptions, Unknowns, and Validation plan, and flag any item left open pending a clarifying answer.
For detailed guidance, examples, and constraints, see references/023-assumption-analysis.md.
Take jabrena/023-assumption-analysis from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.