Results for “causation”

Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode

Analyze complex systems through stocks, flows, and feedback loops to find high-leverage interventions. For organizational, environmental, social, and technical systems exhibiting circular causality. NOT for linear problems or simple cause-effect chains.

Runs a hypothesis-driven debugging workflow that reproduces failures, forms discriminating tests, proves root cause via toggle, and delivers a fix, regression test, and postmortem.

Use to find the causes behind a complaint population and track whether remediation actually stopped them recurring. Trigger for "root cause analysis on our complaints", "why do we keep getting the same complaints", "complaint themes and remediation", recurring complaint categories, complaint reduction programmes, or a remediation that was signed off and did not work.

Maneja exibicao de documento ou coisa — contra a PARTE (CPC 396-400: pedido 397, resposta em 5 dias 398, recusa nao admitida 399, presuncao de veracidade se recusa ilegitima 400) ou contra TERCEIRO (CPC 401-404: citacao em 15 dias, audiencia especial 402, deposito/apreensao 403, escusas 404) — e a arguicao de FALSIDADE documental (CPC 430-433: suscitada na contestacao/replica/15 dias da juntada 430, motivos e meios 431, exame pericial 432, coisa julgada se questao principal 433; onus da prova 429). Use quando o operador disser exibicao de documento, obrigar a apresentar documento, incidente de falsidade, documento falso nos autos, parte esconde documento, exibicao de coisa.

Trigger or resolve a PagerDuty incident for on-call escalation

Find root causes of bugs, test failures, or unexpected behavior before proposing any fixes.

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

Systematic debugging with root cause investigation. (gstack)

Diagnose bugs by establishing a tight feedback loop, tracing root cause, and verifying fixes with regression tests before making changes.

Structured root cause analysis for arriving at a concrete action. Use when something went wrong, a pattern keeps recurring, behavior has drifted, or you catch yourself resolving to "do better" / "remember to X" without a concrete artifact. Five-whys forces behavioral resolutions into file edits, config changes, memory block updates, or scheduled jobs — the action item must produce a diff someone else can verify. Do not use for simple debugging with an obvious cause.

Action (axaz-action)

当需要分析一个观念、文化现象或行为模式为何能广泛传播并被人接受时

Use to clean up sprawling helpdesk tags, categories and custom fields so reporting built on them means something. Trigger for "our tags are a mess", "consolidate our ticket categories", "why don't our tag reports add up", duplicate or near-duplicate tags, tags nobody uses, agents tagging inconsistently, or before building reporting on top of tags.

当需要在写作中与读者建立情感连接、放大问题严重性，并引出后续解决方案时

Understand through recursive decomposition and modular reconstruction of simple operations to reproduce emergent complexity. Use this skill whenever reasoning is required. Framework for [[#parse|parsing]], [[#branch|branching]], [[#reduce|reducing]], [[#ground|grounding]] and [[#emit|emitting]]. Employs metacognitive reasoning epistemology, leveraging first principles through recursive decomposition[^1]. Self-referential and scale-invariant.

Root-cause analysis with hypothesis tracking. Trigger: 'debug', 'broken', 'not working', 'fix this bug', /debug

Redige acao de reparacao de danos por responsabilidade civil — ato ilicito (CC 186) e abuso de direito (CC 187), dever de indenizar (CC 927) com responsabilidade objetiva pela atividade de risco (927 par. unico), extensao do dano e reducao equitativa (CC 944 + par. unico), perdas e danos / lucros cessantes / juros de mora (CC 402-405), danos por homicidio, lesao a saude e ofensa a honra (CC 948-954), distinguindo dano material x moral x estetico x lucros cessantes x perda de chance, pelo rito comum (CPC 319) com tutela se cabivel. Use quando o operador disser quero indenizacao, danos morais, fui lesado, acao indenizatoria, reparacao de danos.

Guides systematic root-cause investigation before proposing fixes for any technical issue, with a four-phase process and red flags to avoid guessing.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Investigating bugs via root cause analysis, reproduction steps, and impact assessment. Investigation-only — finds why bugs occur and where to fix them, no code. Use when a bug needs RCA before a fix.

Create or analyze settings, scenes, world operations, and image direction in the literary cyberpunk mode of William Gibson's Sprawl fiction: dense, accreted urban systems; uneven high technology; corporate power; mediated culture; and human-scale survival inside global networks. Use for Gibson-informed creative work, setting design, or visual briefs, not for generic neon cyberpunk, faithful continuation of named canon, or imitation of Gibson's prose.

Systematically trace bugs backward through call stack to find original trigger

Socratic coach for breaking down problems to fundamental truths. Use when users want to think through a problem deeply, challenge assumptions, or find innovative solutions. Triggers on requests like "help me think through this", "let's break this down", "what are my blind spots", "I'm stuck on a problem", "challenge my assumptions", or explicit requests for first-principles thinking.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

当个人或团队因拖延、分心或动力不足，导致重要目标长期停滞不前，需要一种强制机制来激发高度专注和行动力时