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, so planning starts from a verified problem statement instead of an untested hypothesis. ## Core Features & Use Cases - Framing Separation: Captures the reported observation, the user's stated cause, and the proposed direction as three distinct, preserved items. - Dimension Mapping & Hypothesis Investigation: Builds a map of where the problem could originate and dispatches parallel read-only sub-agents to test each hypothesis against real file:line evidence. - Frame Brief Artifact: Produces a structured frame.md document 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 dashboard is broken, let's rewrite the data layer." The Skill investigates whether the issue actually lives in the data layer, the query, the cache, or the rendering, and confirms or reframes the problem before any plan is written. ## Quick Start Invoke the frame skill with a description of the bug or scope question you are about to plan, and let it verify the framing before you commit to a solution.