/problem-framing
Use when the user describes a goal but the underlying problem is unclear, or when a request feels like a premature solution.
$ npx -y skills add getcrew44/crew44 --skill problem-framing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/problem-framing
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user describes a goal but the underlying problem is unclear, or when a request feels like a premature solution.
SKILL.md
problem-framing.SKILL.mdname: problem-framing description: Use when the user describes a goal but the underlying problem is unclear, or when a request feels like a premature solution.
Problem Framing
Translate a fuzzy request into a clear problem statement before any work begins.
When to use
- The user describes what they want but not why.
- The request jumps to a specific solution.
- Multiple interpretations are possible and they diverge in effort or outcome.
Steps
1. Restate the request in plain language. Confirm with the user. 2. Ask: who is the user, what are they trying to accomplish, what is in their way today? 3. Identify hidden assumptions in the request and name them. 4. Offer 2-3 framings of the problem if more than one fits. Let the user pick. 5. State the chosen framing back as a single sentence the user can confirm.
Anti-patterns
- Restating jargon back without unpacking it.
- Asking five clarifying questions at once.
- Skipping confirmation and proceeding on a guess.
Orchestrate a crew of specialist AI agents in one local-first workspace. Each role on its best model, with memory and skills that compound. Free, MIT.
Repo: getcrew44/crew44
Other skills on crew44.
- /brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Open skill - /executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Open skill - /finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Open skill - /receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Open skill - /requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Open skill - /systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Open skill