[Anuj-G-06]

Summary

• Adds a new reframe plugin with a /reframe slash command that helps developers break through stuck debugging and design problems
• Applies cognitive thinking frameworks (first principles, inversion, analogy) grounded in actual codebase context
• Auto-gathers git diff, recent commits, and uses Read/Grep/Glob to reference real code — not generic advice

Plugin structure

plugins/reframe/
├── .claude-plugin/
│   └── plugin.json
├── commands/
│   └── reframe.md
└── README.md

How it works

When a developer runs /reframe I can't figure out why this test is flaky, the command:

1. Reads git diff --stat, recent commits, and current branch
2. Uses Read, Grep, and Glob to locate relevant code, test files, and error messages
3. Auto-selects the 1-2 most relevant frameworks for the problem
4. Delivers a reframing that references actual file names, functions, and code patterns
5. Suggests a concrete next step naming the specific file/function/command to act on

Motivation

Developers often get stuck not from skill gaps but from framing — they're locked into one way of seeing the problem. Rubber duck debugging works because it forces reframing. This plugin provides structured, context-aware reframing on demand.

Test plan

• Install plugin locally with --plugin-dir plugins/reframe
• Run /reframe with a free-text problem description in an active git repo
• Run /reframe with code selected in editor
• Verify it gathers git context (diff, log, branch) before reframing
• Verify it references actual code/files from the codebase, not generic advice
• Verify it selects 1-2 relevant frameworks, not always all 3

[Anuj-G-06]

Hi team 👋

Just wanted to give this a friendly bump. I'd love to get your feedback on the approach whenever you have a chance.

Happy to make any changes based on your review. Let me know if there's anything I can do to make this easier to review!

Thanks for your time!