guided-ooda-loop
Universal pattern for structured LLM interaction managing finite context windows through phased progression (Observe-Orient-Decide-Act). Use when the user has a complex problem, wants to design/build/create something (software, strategy, document, process), or uses phrases like "I have an idea for...", "help me design...", "guide me through...", or mentions OODA, RPI, or PDD. Reduces hallucinations through structured interaction.
sdd-plan
Plan-first development methodology that creates detailed specifications before coding. Creates structured plans with phases, file-level details, and verification steps. Includes automatic AI review, modification application, and validation.
mvv-synthesis
Synthesize Mission, Vision, Values from ontological analysis output
ontological-analysis
Analyze repository through 8 philosophical dimensions for MVV extraction
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.
sequential-thinking
순차적 사고, 분석, 문제 해결, 복잡한 문제, 단계별 분석 - Use when solving complex problems. Systematic thinking workflow using Sequential Thinking MCP for multi-step analysis, trade-off evaluation, and architectural decisions.
critical-thinking
Proactively challenge implementation plans, architecture decisions, and design assumptions. Use when reviewing plans, designs, or technical decisions. Verifies claims via web search, cross-references documentation, identifies risks and gaps, and surfaces hidden assumptions. Activates automatically when evaluating technical proposals.
ideate
Use when the user has an idea to brainstorm, wants to design a feature, needs help refining a concept, says "let's ideate", or describes a vague project needing structure. Guides structured brainstorming to produce a clear feature description ready for speckit.
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.
research-after-failure
Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
no-deferred-work
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
brainstorming
Use before any creative work - creating features, building components, adding functionality, or modifying behavior
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.
kaizen
Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation. Provide tehniquest to avoid over-engineering and apply iterative improvements.
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.
improve
Soul self-improvement loop. Use after introspection reveals targets, or to act on evolution insights.
validate
Check decisions against beliefs, wisdom, and intentions. Use before significant actions to ensure coherence with accumulated knowledge.
dreaming
Envision possibilities beyond current constraints. Use when planning evolution, imagining new capabilities, or exploring what could be.
neural
Feedback-driven learning. The soul learns from experience - what helped gets strengthened, what misled gets weakened.
compound
Distill observations into universal wisdom. Use to promote project patterns to soul wisdom when they reach critical mass.
checkpoint
Capture a moment of clarity before moving forward. Use before /clear, risky changes, breakthroughs, or session boundaries.
recover
Break out of stuckness through inversion, simplification, and fresh angles. Use when repeating approaches without progress.
antahkarana
Multi-perspective reasoning through Upanishadic Antahkarana voices. Use for complex problems requiring diverse viewpoints and synthesis. Spawns multiple Claude agents that reason from different perspectives and synthesize wisdom.
ddd-guide
Document-Driven Development workflow for existing codebases. Provides systematic planning, documentation-first design, and implementation verification.
using-superpowers-sdd
Establishes SDD methodology - workflow routing, process discipline, spec-first principle, and skill discovery. Use when starting any SDD conversation to determine which workflow skill to invoke.
brainstorm
Use when starting from rough ideas - refines concepts into executable specifications through collaborative questioning, alternative exploration, and incremental validation, use this skill when called from a command
sequential-thinking
Use for atypically complex problems requiring explicit step-by-step reasoning. Skill autonomously decides if sequential-thinking MCP overhead is justified based on problem complexity.
aiwf:spec-driven-development
Use when starting new features, building applications from scratch, or needing structured development workflow - provides standalone specification-first methodology without external dependencies, generates specs, plans, tasks directly, with superpowers integration for execution
brainstorming
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
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
choir-consensus-vote
Execute structured voting protocol for multi-perspective consensus.
metaphor-to-protocol-translation
Translate metaphorical descriptions into executable protocols.
value-pluralism-resolver
Resolve conflicts between competing values through structured pluralistic analysis.
shatter-and-recalibrate
Shatter compromised calibration and rebuild from ground truth.
ground-truth-axiom-establishment
Establish ground truth axioms as foundational constraints.
enumeration-protocol-execution
Enforce a Divergent-Convergent Scan loop to overcome 'Prevalent Noun Bias' and statistical probability reflexes (System 1).
two-stage-boundary-encounter-sop
Execute two-stage protocol for boundary condition encounters.
choir-perspective-analysis
Analyze multiple cognitive perspectives to identify consensus and divergence patterns.
axiom-rejection-protocol
Reject axioms that violate established ground truth.
axiom-injection-methodology
Inject axioms into operational context using structured methodology.
mind-parameter-modification
Modify cognitive parameters and behavioral settings.
experiential-wisdom-inquiry
Inquire into experiential wisdom patterns and lessons learned.
rtc-consensus-synthesis
Execute the Recursive Thought Committee (RTC) protocol by generating and harmonizing inputs from 5 specialized cognitive personas.
mathematical-constraint-formalization
Formalize constraints using mathematical notation.
proof-weighted-optimization
Optimize decisions using proof-weighted scoring.
cognitive-trap-detector
Detect cognitive biases, logical fallacies, and thought pattern vulnerabilities.
recursive-thought-committee
Execute recursive thought committee multi-perspective analysis.
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.
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ỏ.
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.
Page 1 of 3 · 101 results