10x-frame

Challenge problem framing assumptions before planning implementation work.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/Assamir/ai-toolkit --skill 10x-frame-assamir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-frame
Source: https://github.com/Assamir/ai-toolkit/tree/main/.cursor/skills/10x-frame
Command: npx skills add https://github.com/Assamir/ai-toolkit --skill 10x-frame-assamir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often plan and build perfect solutions to the wrong problem because the observation and the assumed cause get treated as one fact. This Skill separates what is actually observed from what is assumed before any planning begins, preventing wasted effort on misframed tasks. ## Core Features & Use Cases - Framing Separation: Captures the reported observation, the user's stated cause, and the proposed direction as three distinct items so assumptions stay visible. - Hypothesis Investigation: Builds a dimension map of where the problem could originate and dispatches parallel read-only sub-agents to gather file:line evidence for each hypothesis. - Frame Brief Output: Produces a structured frame.md artifact with a hypothesis evidence table, confidence rating, and a reframed or confirmed problem statement ready to hand off to planning. - Use Case: A user reports "the sync is broken, let's rebuild the retry logic." This Skill investigates whether the retry logic is actually at fault, discovers the real issue lives in the event ordering layer, and hands a corrected problem statement to the planning step. ## Quick Start Ask the assistant to run /10x-frame on your bug report or scope question before starting any implementation planning.

Frequently Asked Questions about 10x-frame

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

FAQPage Schema
How do I validate a problem statement before planning a fix?

Run the framing step on your observation and proposed fix. It separates the literal observation from your assumed cause, maps alternative dimensions where the problem could originate, and investigates each with evidence before confirming or reframing the problem.

What is the difference between framing and planning a task?

Framing determines what the right problem to solve is, while planning determines how to build the solution. Framing asks where in the system the problem actually lives; planning asks which implementation approach to take. Framing always runs first.

When should I skip the framing step?

Skip it for purely mechanical changes like renaming a function or bumping a dependency version, when you have already verified the root cause yourself, or when the request is a clearly scoped feature with no underlying premise to challenge.

What happens if the framing investigation confirms my original assumption?

A confirmed framing is a successful outcome. The Frame Brief explicitly states that the initial framing held up, and you proceed with your originally proposed direction rather than manufacturing an unnecessary reframing.

Can the Frame Brief be used without the planning step?

Yes. The Frame Brief is a standalone artifact useful as a discussion document or to scope a quick fix. It does not require a follow-on planning step, though it is designed to serve as direct input to one.