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.