Agent skill

think-reframe

Problem redefinition before problem solving. Takes a stated problem, extracts its premises, then spawns reframers applying different lenses (problem-vs-symptom, scope-shift, stakeholder-shift, level-of-abstraction, time-horizon, inversion, category-shift, constraints-shift) in isolation, and synthesizes the alternatives into a report with an orchestrator recommendation. Produces feedback only — no code, no tickets, no artifacts.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill think-reframe --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/analysis/think-reframe/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Think-Reframe - Problem Redefinition Before Problem Solving Takes a stated problem and explores alternative framings of it through parallel reframers, each applying a different reframing lens in isolation. The output is a set of candidate reframings with an explicit recommendation: keep the original framing, adopt a specific reframing, or explore further. Sits upstream of `/think-brainstorm` in the natural reasoning pipeline — most wasted engineering effort goes into solving well-defined versions of the wrong problem, and this skill is the dedicated defense against that failure mode. **This skill produces no tangible artifacts.** It is a consultant, not an implementer. No code, no tickets, no commits. The output is a structured reframing report that the user can act on by refining their problem statement or proceeding with the original. ## Roles **Judge (you, running this skill):** - Capture the stated problem in a written brief - Extract stated and unstated premises (lightweight reconnaissance, not confrontation) - Choose appropriate reframing lenses - Spawn reframers and synthesize the alternatives into a report with a recommendation **Reframers:** Each receives a specific lens

What's inside
Steps it walks through
  1. Roles
  2. Workflow
  3. 1. Receive the Problem
  4. 2. Extract Premises
  5. 3. Choose Reframing Lenses
  6. 4. Spawn Reframers (Parallel, Isolated)
  7. 5. Synthesize
  8. 6. Report
  9. 7. No Iteration
  10. Constraints
  11. When to Use
  12. Relationship to Other Skills
  13. Philosophy
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the think-reframe skill do?

Problem redefinition before problem solving. Takes a stated problem, extracts its premises, then spawns reframers applying different lenses (problem-vs-symptom, scope-shift, stakeholder-shift, level-of-abstraction, time-horizon, inversion, category-shift, constraints-shift) in isolation, and synthesizes the alternatives into a report with an orchestrator recommendation. Produces feedback only — no code, no tickets, no artifacts.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill think-reframe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going