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 starts, preventing wasted effort on misframed work. ## Core Features & Use Cases - Framing Separation: Captures the reported observation, the user's stated cause, and the proposed direction as three distinct items that stay separate throughout the analysis. - Hypothesis Investigation: Builds a dimension map of where the problem could originate, then dispatches parallel read-only sub-agents to test each hypothesis against actual code and documents with file:line evidence. - 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 API is slow, let's add caching." The Skill investigates whether the bottleneck is actually caching-related, discovers an N+1 query pattern instead, and reframes the problem before any plan is written. ## Quick Start Invoke the frame skill with a problem description or change ID, for example by asking to challenge the framing of a bug report before planning the fix.
