10x-frame

Separate observations from causes and validate root-cause hypotheses before planning solutions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps clarify the underlying problem before planning a solution, ensuring that the proposed fix addresses the correct issue.

Core Features & Use Cases

  • Problem Framing: Separate observations from stated causes and solutions.
  • Dimension Mapping: Identify potential root causes based on system context.
  • Hypothesis Testing: Investigate each potential cause for evidence.
  • Reframing: Provide a reframed problem statement for accurate planning.
  • Use Case: When a user reports a bug or issue, this Skill helps determine the actual problem before proceeding with a fix.

Quick Start

Frame the problem of a broken feature before planning a fix using the /10x-frame command.

Frequently Asked Questions about 10x-frame

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

FAQPage Schema
How do I perform root cause analysis before fixing a bug?

Root cause analysis before bug fixing requires separating initial observations from assumed causes. By validating assumptions and testing hypotheses against system context, you can identify the actual underlying issue before planning a solution.

What is the best way to challenge assumptions during problem framing?

Challenging assumptions during problem framing involves mapping system dimensions and investigating evidence for each potential cause. This validation process provides a reframed problem statement to ensure accurate solution planning.

How do I separate observations from stated causes when investigating an issue?

Separating observations from stated causes involves analyzing the initial problem report to distinguish factual symptoms from assumed reasons. This hypothesis testing approach validates evidence before you proceed with a fix.

When do I need to validate assumptions for scope challenges and design decisions?

Validating assumptions for scope challenges and design decisions is necessary whenever a proposed solution is planned. It ensures the underlying problem statement is accurate and the planned scope directly addresses the correct issue.

Can I use problem framing to reframe a broken feature report?

You can use problem framing to reframe a broken feature report by analyzing the user input to separate symptoms from causes. This produces a validated problem statement for accurate planning.

Why does planning a solution without hypothesis testing lead to incorrect bug fixes?

Planning a solution without hypothesis testing risks incorrect bug fixes because unvalidated assumptions may mask the actual root cause. Analyzing system context and evidence ensures the planned fix targets the correct issue.