brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
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.
/problem-framingContext 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.
name: 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.
Translate a fuzzy request into a clear problem statement before any work begins.
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.
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
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent,…
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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…
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes