10x-frame

Invoke the frame skill with your observation and proposed fix. It separates the observation from your assumed cause, maps alternative dimensions where the problem could originate, and investigates each with evidence before confirming or reframing the problem.

Framing determines what the right problem to solve is, while planning determines how to build the solution. This Skill handles only framing and explicitly never proposes implementation approaches, phases, or file changes; its output feeds into a separate planning step.

Skip framing for purely mechanical changes like renaming a function or bumping a dependency version, or when you have already verified the root cause yourself. The skill is designed for bug-shaped, scope-shaped, or assumption-shaped inputs where the premise is unverified.

It writes a single Frame Brief markdown file to context/changes/<change-id>/frame.md containing the preserved original framing, a dimension map, a hypothesis evidence table, a confidence rating, and a reframed or confirmed problem statement.

Confirming the original framing is an explicitly allowed and successful outcome. The brief states that the initial framing held up and recommends proceeding with the originally proposed direction rather than manufacturing an unnecessary reframing.