10x-frame

Separate observation from cause and reframe problem statements.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Dergacz/AI_CV_Builder --skill 10x-frame-dergacz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-frame
Source: https://github.com/Dergacz/AI_CV_Builder/tree/main/.claude/skills/10x-frame
Command: npx skills add https://github.com/Dergacz/AI_CV_Builder --skill 10x-frame-dergacz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in separating the observation from the stated cause and the problem from the proposed solution, ensuring that the right problem is planned for before any solution is implemented.

Core Features & Use Cases

  • Separation of Observation and Cause: Helps to distinguish between what is observed and what is assumed to be the cause.
  • Dimension Mapping: Identifies the possible origins of an observation to understand the problem space better.
  • Hypothesis Testing: Investigates each plausible dimension to determine the most likely cause of the observation.
  • Reframing: Provides a reframed problem statement that aligns with the actual issue at hand.
  • Use Case: When faced with a bug report, this Skill can help determine whether the proposed fix addresses the root cause or if a deeper investigation is needed.

Quick Start

Use the 10x-frame skill to analyze the issue described in the bug report 'bug-123.md'.

Frequently Asked Questions about 10x-frame

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I separate root cause from observation when analyzing a bug report?

This Skill reframes problem statements by separating observation from assumed cause, mapping possible origins of the observation, testing each plausible dimension, and outputting a refined problem statement that targets the actual issue rather than the proposed solution.

What is the best way to reframe a problem statement before implementing a software fix?

Reframing a problem statement requires separating the observation from the stated cause and the problem from the proposed solution. This ensures you plan for the right problem before implementing any software development fix.

Does this approach work for requirement analysis or only for debugging?

This approach works for both debugging and requirement analysis. It applies broadly to software development by analyzing the context of a problem statement to ensure proposed fixes or requirements align with the actual issue rather than stated assumptions.

How do I use problem framing to investigate dimensions of a bug?

To investigate bug dimensions using problem framing, the Skill analyzes the provided issue context, identifies possible origins of the observation, and tests each plausible hypothesis to determine the most likely cause before outputting a reframed problem statement.

When should I not use root cause analysis on a bug report?

You should avoid this root cause analysis when the bug report already contains a verified root cause and a matching solution, as the Skill is designed to challenge assumptions and separate observations from proposed solutions before planning begins.