10x-frame

Challenges problem framing by separating observations from stated causes before planning begins.

Updated May 20, 2026
One-click install
npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-frame-zawilecxd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-frame
Source: https://github.com/ZawilecxD/trAInR/tree/main/.cursor/skills/10x-frame
Command: npx skills add https://github.com/ZawilecxD/trAInR --skill 10x-frame-zawilecxd

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about 10x-frame

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a problem statement before planning a fix?

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

What is the difference between problem framing and implementation planning?

Framing determines what the right problem to solve is, while planning determines how to build the solution. This Skill only produces a reframed or confirmed problem statement; it never proposes implementation approaches, phases, or file changes.

When should I skip problem framing and go straight to planning?

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. Framing adds the most value for bug-shaped, scope-shaped, or assumption-shaped inputs.

Can the framing process conclude that my original assumption was correct?

Yes. Confirming the initial framing is an explicitly allowed and successful outcome. The Skill avoids manufactured reframings and only overrides your framing when evidence from the actual codebase supports a different hypothesis.

What artifact does the framing investigation produce?

It writes a Frame Brief to context/changes/<change-id>/frame.md containing the preserved original framing, a dimension map, a hypothesis evidence table with verdicts, a confidence rating, and guidance for the subsequent planning step.