What problem does it solve? Teams often plan 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, then dispatches parallel read-only sub-agents to test each hypothesis against real code and documents with file:line evidence. - Frame Brief Output: Produces a structured brief in context/changes/<change-id>/frame.md with a hypothesis evidence table, confidence rating, and a reframed or confirmed problem statement ready to hand off to /10x-plan. - Use Case: A user says "the dashboard is broken, let's rewrite the query." The skill investigates whether the issue is the query, the data pipeline, or the classification logic, and may reframe the problem before any plan is written. ## Quick Start Run /10x-frame with a description of the bug or scope question you are about to plan, and answer its clarifying questions before planning begins.
