“systemic”的搜索结果

Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.

中文简介正在准备中。当前显示原文说明。

Investigate root causes and manage CAPAs (Corrective and Preventive Actions) for compliance deviations. Covers investigation method selection (5-Why, fishbone, fault tree), structured root cause analysis, corrective vs preventive action design, effectiveness verification, and trend analysis. Use when an audit finding requires a CAPA, when a deviation or incident occurs in a validated system, when a regulatory observation needs a formal response, when a data integrity anomaly requires investigation, or when recurring issues suggest a systemic root cause.

中文简介正在准备中。当前显示原文说明。

Orchestrate a whole-registry sweep of Gaia — fan out 13 parallel audit agents across every skill, run adversarial verification, surface Semantic Fusion candidates, propose new generic skill references, and synthesize a publish-ready HTML report under docs/meta/reports/. Use this skill for broad, systemic analysis across many skills at once: "run a meta sweep", "sweep the meta", "full meta audit", "audit the whole registry against META.md", "widespread nomenclature issues", "find all skills missing a GitHub link", "produce a meta report", "check for evidence type mismatches across the registry", "find skills that document a third-party tool with no attribution", or explicitly types /gaia-meta-sweep. This is the registry-wide macro companion to /gaia-meta-audit (a prioritized queue, single-pass) and /gaia-audit (fixes one skill). Use it when you need the full surface — 13 audit dimensions, adversarial verification, fusion proposals, and a durable findings artifact — not just a queue.

中文简介正在准备中。当前显示原文说明。

Turn a moment of friction — a conflicting PR, a wedged runner, a mysterious red check, a repeated manual chore — into a durable, actionable report. Sizes up the scenario, captures the evidence, separates one-off from SYSTEMIC, proposes a fix, and routes it (fix now, or hand off). Reports are LIVING documents that the fixing agent updates with the outcome. Invoke whenever something feels like it shouldn't have been this hard, or when the same annoyance shows up twice.

中文简介正在准备中。当前显示原文说明。

Use when a task needs the judgment of a Certified Anesthesiologist Assistant (CAA) working inside an Anesthesia Care Team — building and executing an intraoperative anesthetic plan under a directing anesthesiologist, reading a vital-sign trend for anesthesia-specific emergencies (malignant hyperthermia, local anesthetic systemic toxicity, awareness), deciding when a deviation is an immediate-escalation trigger versus an independently correctable event, or navigating the jurisdiction/concurrency limits of CAA practice.

中文简介正在准备中。当前显示原文说明。

Use when a task needs the judgment of a board-certified anesthesiologist — building a preoperative anesthesia plan and risk stratification, choosing general vs. regional technique and airway strategy, managing an intraoperative crisis (difficult airway, malignant hyperthermia, local anesthetic systemic toxicity), or writing a PACU handoff and postoperative pain-management order set.

中文简介正在准备中。当前显示原文说明。

Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.

中文简介正在准备中。当前显示原文说明。

Aggregate friction log files across a time period to identify recurring patterns, classify each cluster by intervention type, produce a prioritized action plan with success criteria, and calculate convergence metrics. Complements `skmtc-retro` (which captures per-session signal) by acting as the system's actuator: turning accumulated observations into decisions. The primary output is a review document that makes the "is it getting better?" question answerable. Use this skill when the user asks to "review retros", "review friction", "run a retro review", "what's the pattern across sessions", "what should we fix next", or on a periodic cadence (monthly, pre-release). Also run after a cluster of sessions on the same feature area to surface systemic issues before they compound. Distinct from `skmtc-retro` — that skill captures per-session observations; this skill synthesizes them into decisions. Do not run this skill as a substitute for a per-session retro.

中文简介正在准备中。当前显示原文说明。

Performs root cause analysis on DAG execution failures. Traces failure propagation, identifies systemic issues, and generates actionable remediation guidance. Activate on 'failure analysis', 'root cause', 'why did it fail', 'debug failure', 'error investigation'. NOT for execution tracing (use dag-execution-tracer) or performance issues (use dag-performance-profiler).

中文简介正在准备中。当前显示原文说明。

Resolve a verified cluster of Rembric issues from causal root to evidence-gated closure. Use after systemic triage identifies a shared root, or when the user asks to attack issues at the root, create a mechanism map, plan a deletion-first fix, or close a fixed/stale issue cluster. Use `diagnose` for a single defect whose reproduction is not yet established.

中文简介正在准备中。当前显示原文说明。

Investigate the root cause of a recurring or systemic defect across a series of incidents, not a single one. Use on the third recurrence, or when someone asks 'why again?', 'five whys', 'fix the root'. Skip for one or two ordinary cases, an already proven simple cause, or a one-off external outage. Triggers: /five-whys, five whys, fix the root.

中文简介正在准备中。当前显示原文说明。

Сравнение четырех психотерапевтических методов, утвержденных директивами в Германии: когнитивно-поведенческая терапия, психодинамическая терапия, психоанализ, системная терапия — Ориентировочное руководство.

中文简介正在准备中。当前显示原文说明。

德国四种法定医保资助的心理治疗取向对比：认知行为疗法、深层心理学取向心理治疗、精神分析、系统疗法 — 定向指南。

中文简介正在准备中。当前显示原文说明。

Genogram work: Recognizing and reflecting on family relationship patterns. Multigenerational perspective, genogram symbols, pattern recognition, and resources in family history.

中文简介正在准备中。当前显示原文说明。

Trabajo con genogramas: Reconocimiento y reflexión sobre los patrones de relaciones familiares. Perspectiva multigeneracional, símbolos del genograma, reconocimiento de patrones y recursos en la historia familiar.

中文简介正在准备中。当前显示原文说明。

ジェノグラム（家族関係図）ワーク：家族の関係性パターンの把握とリフレクション。多世代的視点、ジェノグラム記号、パターン認識、家族史におけるリソース。

中文简介正在准备中。当前显示原文说明。

Работа с генограммой: Распознавание и осмысление паттернов семейных отношений. Межпоколенческая перспектива, символы генограммы, выявление паттернов и ресурсы в истории семьи.

中文简介正在准备中。当前显示原文说明。

家系图（Genogram）工作：识别与反思家庭关系模式。跨世代视角、家系图符号、模式识别以及家庭历史中的资源。

中文简介正在准备中。当前显示原文说明。

Comparativa de los cuatro enfoques psicoterapéuticos reglamentarios en Alemania: Terapia Cognitivo-Conductual, Psicoterapia de Orientación Psicodinámica, Psicoanálisis y Terapia Sistémica — Guía de orientación.

中文简介正在准备中。当前显示原文说明。

ドイツにおける公的医療保険適用対象の4つのガイドライン療法（認知行動療法、精神力動的心理療法、精神分析、システム療法）の比較 — オリエンテーションガイド。

中文简介正在准备中。当前显示原文说明。

Systemische Fragetechniken: Zirkuläre Fragen, Skalierungsfragen, Wunderfrage und Ausnahmefragen zur Reflexion und Perspektiverweiterung.

中文简介正在准备中。当前显示原文说明。

Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.

中文简介正在准备中。当前显示原文说明。

Think through the consequences of consequences — not just what happens immediately, but what happens next, and next after that, across time. Load when a decision looks obviously good or obviously bad on initial read, when the user is optimising for a short-term outcome that might create a long-term problem, when unintended consequences are a concern, or when deep-thinking diagnoses a second-order frame. Triggers on "what are the downstream effects", "what happens after that", "unintended consequences", "think ahead on this", "long-term vs short-term", or "what comes after that". Based on Howard Marks second-level thinking and Farnam Street mental models. Most powerful for decisions with delayed consequences or systemic effects.

中文简介正在准备中。当前显示原文说明。

[00] TnR ABSOLUTE RIGOR — Systemic Verification Doctrine. Forced cognitive exertion for high-stakes investigations. Mandates absolute deconstruction, mathematical proof chains, and ≥95% derived certainty. Zero-tolerance for heuristics or sentiment-based reasoning. Shortcuts are defined as intentional hallucinations.

中文简介正在准备中。当前显示原文说明。