systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
pathology-koan-generator
Generate diagnostic koans to test reasoning boundaries and edge cases.
enumeration-protocol-execution
Enforce a Divergent-Convergent Scan loop to overcome 'Prevalent Noun Bias' and statistical probability reflexes (System 1).
sequential-thinking
Apply structured, reflective problem-solving for complex tasks requiring multi-step analysis, revision capability, and hypothesis verification. Use for complex problem decomposition, adaptive planning, analysis needing course correction, problems with unclear scope, multi-step solutions, and hypothesis-driven work. | Sử dụng khi: suy nghĩ từng bước, phân tích, vấn đề phức tạp, chia nhỏ.
Problem-Solving Techniques
Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application. | Dùng khi giải quyết vấn đề, tìm giải pháp, phân tích, tối ưu, thuật toán, bị kẹt.
research
Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable. | Sử dụng khi: nghiên cứu, tìm hiểu, khám phá, học về, tài liệu.
sequential-thinking
Dynamic problem-solving through structured sequential thoughts. Use when breaking down complex problems, planning multi-step solutions, analyzing ambiguous requirements, debugging intricate issues, exploring design alternatives, or tackling problems where the full scope is unclear. Enables thought revision, branching, and iterative refinement.
brainstorm
Interactive idea refinement using Socratic questioning methodology. This skill should be used when users want to explore an idea, find gaps in concepts, enhance proposals, or structure thoughts before implementation planning. Triggers on "brainstorm", "explore this idea", "find holes in", "help me think through", "what am I missing", or when presenting rough concepts that need refinement. Output integrates with create-plan skill.
analyze-frame
當接收到新需求或 Event Storming 產出後觸發。分析問題類別（CBF/IDF/RIF），生成完整的規格目錄結構。實現「需求與實作分離」、「規格即文檔、文檔即規格」。
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
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.
sub-issue-maker
Provide the task granularity for cutting subissues.
user-discovery-research
Master user research methodologies, customer interviews, persona development, and journey mapping. Understand customer problems deeply before building.
chain-of-thought
Step-by-step reasoning patterns for complex problem solving
brainstorming
>-
debug
Expert debugging methodology. Triggers on debug, investigate, fix bug, troubleshoot.
sequential-thinking
Use when complex problems require systematic step-by-step reasoning with ability to revise thoughts, branch into alternative approaches, or dynamically adjust scope. Ideal for multi-stage analysis, design planning, problem decomposition, or tasks with initially unclear scope.
brainstorming
Use when starting any feature, project, or design work. Guides collaborative design refinement through incremental questioning before any code is written.
Page 2 of 3 · 37 results