Skip to content
cccskills
FreePublished on GitHub

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md3.3 KB
  • references/023-assumption-analysis.md5.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

  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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use 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 project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth455Updated Oct 22, 2026

Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth455Updated Oct 22, 2026

Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth455Updated Oct 22, 2026

Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth455Updated Oct 22, 2026

Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or .codex/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .github/agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Bootstrap .codex/agents; Copy robot agents. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth455Updated Oct 22, 2026

Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

jabrena/plinth455Updated Oct 22, 2026

See all skills by jabrena

Report a problem with this skill