Results for “problem-solving”

Computational thinking as a problem-solving discipline independent of programming languages. Covers the four pillars (decomposition, pattern recognition, abstraction, algorithm design), computational problem-solving methodology (understand, decompose, generalize, formalize, verify), abstraction levels (from hardware through user interface), modeling and simulation, automata and formal languages (DFA, NFA, regular expressions, context-free grammars, Turing machines), computational complexity classes (P, NP, NP-complete, undecidable), and constructionist pedagogy (learning by building, Logo, Scratch, physical computing). Use when approaching unfamiliar problems, teaching problem-solving strategies, analyzing problem complexity, or bridging between domain knowledge and computational solutions.

The English summary is being prepared. Showing the original description.

Apply systematic problem-solving techniques for marketing challenges including campaign complexity (simplification cascades), creative blocks (collision-zone thinking), recurring campaign patterns (meta-pattern recognition), assumption constraints (inversion exercise), audience scale uncertainty (scale game), and dispatch when stuck. Techniques derived from proven problem-solving frameworks adapted for marketing execution.

The English summary is being prepared. Showing the original description.

Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification

The English summary is being prepared. Showing the original description.

Dispatch to the right problem-solving technique based on how you're stuck

The English summary is being prepared. Showing the original description.

Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.

The English summary is being prepared. Showing the original description.

Design the transition from worked examples to independent problem-solving using expertise-reversal principles. Use when students follow examples but cannot solve problems alone.

The English summary is being prepared. Showing the original description.

Dispatch to the right problem-solving technique based on how you're stuck

The English summary is being prepared. Showing the original description.

Apply systematic problem-solving methodologies to complex challenges. Use when the user says "guide me through structured problem solving" or "I want to crack this challenge with guided problem solving techniques"

The English summary is being prepared. Showing the original description.

Design the transition from worked examples to independent problem-solving using expertise-reversal principles. Use when students follow examples but cannot solve problems alone.

The English summary is being prepared. Showing the original description.

Dispatch to the right problem-solving technique based on how you're stuck

The English summary is being prepared. Showing the original description.

Creative problem-solving techniques for breaking through stuck points - includes collision-zone thinking, inversion, pattern recognition, and simplification

The English summary is being prepared. Showing the original description.

Dispatch to the right problem-solving technique based on how you're stuck

The English summary is being prepared. Showing the original description.

Use when stuck on approach (not debugging). Strategic unsticking via 7 non-default techniques: simplification cascades, collision-zone thinking, meta-pattern recognition, inversion, scale game, first principles, via negativa. Triggers on complexity spiraling, innovation block, recurring patterns across domains, forced-assumption solutions, scale uncertainty, told-it's-impossible, or bloated systems needing subtraction. For evidence-based root-cause debugging, use mk:sequential-thinking instead.

The English summary is being prepared. Showing the original description.

Structured problem solving in 6 steps: Problem definition, goals, brainstorming, evaluation, implementation, and review.

The English summary is being prepared. Showing the original description.

6つのステップによる構造化問題解決：問題の定義、目標設定、ブレインストーミング、評価、実行、効果検証。

The English summary is being prepared. Showing the original description.

六步骤结构化问题解决：问题定义、目标设定、头脑风暴、方案评估、实施与效果复盘。

The English summary is being prepared. Showing the original description.

Resolución estructurada de problemas en 6 pasos: Definición del problema, objetivos, lluvia de ideas, evaluación, implementación y revisión.

The English summary is being prepared. Showing the original description.

Структурированное решение проблем в 6 шагов: Определение проблемы, постановка целей, мозговой штурм, оценка, реализация и проверка результатов.

The English summary is being prepared. Showing the original description.

Resolve complex or high-impact problems when the cause, solution path, requirements, or proof boundary is genuinely uncertain. Use when work needs evidence-led diagnosis, consequential design or implementation, or a completion audit; do not trigger merely because work has multiple steps, or for simple facts, fully specified routine changes, or pure creative generation.

The English summary is being prepared. Showing the original description.

Define reusable reasoning and decision patterns for agents, embed them in executable workflows, and review their performance. Share successful approaches, including conditional decision trees, stepwise problem solving, analogies, and evaluation from multiple perspectives.

• Define conditional rules for agent decisions
• Turn problem-solving steps into executable workflows
• Solve new problems using similar past cases

Helps AI agents recover from repeated failures by reviewing previous attempts, checking original sources, testing different hypotheses, and verifying results. It combines structured troubleshooting with performance review rhetoric modeled on large technology companies.

• Breaking out of repeated failed attempts
• Investigating configuration or deployment failures
• Verifying an agent's claimed completion

Structure problem solving around clear goals, competing explanations, experiments, and measurable results. Use the cycle to diagnose bugs, validate features, compare prompts, or evaluate an early product, then choose the next step based on evidence.

• Diagnosing a bug with a quick investigation
• Comparing prompt structures through experiments
• Defining success criteria for a feature

Problem-solving strategies for connectedness in topology

The English summary is being prepared. Showing the original description.

Problem-solving strategies for compactness in topology

The English summary is being prepared. Showing the original description.