메뉴
Interpret DSDS simulation outputs including summary metrics, per-node time series, traces, causal graphs, and invariant breaches. Use when reviewing run results, comparing design alternatives, diagnosing bottlenecks, and proposing mitigation steps.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | simulation-output-analyst |
| description | Interpret DSDS simulation outputs including summary metrics, per-node time series, traces, causal graphs, and invariant breaches. Use when reviewing run results, comparing design alternatives, diagnosing bottlenecks, and proposing mitigation steps. |
Analyze DSDS run outputs to identify bottlenecks, cascade roots, and mitigation priority. Produce evidence-backed findings from summary metrics, time series, traces, and causal artifacts.
Now: stop-the-bleed changes.Next: structural fixes.Later: optimization and cost tuning.references/output-analysis-playbook.md for checklist and report template.docs/SYSTEM_OVERVIEW.md (analysis layer expectations)canonical-catalogue/DSDS Canonical Catalogue - Metrics & SLIs.csvcanonical-catalogue/DSDS Canonical Catalogue - Simulation outputs.csvplanning/IMPLEMENTATION_PLAN.md (Phase 6)Design DSDS chaos experiments with deterministic setup, explicit hypotheses, and measurable outcomes. Use when planning failure drills, resilience validation, pre-production risk exercises, and repeatable chaos scenarios for regression testing.
Map architecture requirements to valid DSDS component categories and component types. Use when converting system requirements into simulator node selections, resolving ambiguous type choices, and ensuring required attributes are captured before topology authoring.
Map DSDS architectures across AWS, GCP, and Azure equivalents and estimate cost-impact tradeoffs. Use when planning provider portability, comparing cloud options, and explaining cost/performance implications of design choices.
Convert DSDS UI specs, mock HTML screens, and system docs into concrete frontend component implementation tasks. Use when turning design references into React components, hooks, state contracts, and acceptance criteria.
Analyze likely cascade paths and propagation semantics in DSDS architectures. Use when estimating blast radius, diagnosing multi-hop degradation, validating containment strategies, or explaining how a localized failure can become systemic.
Define and evaluate deterministic invariants and policy checks for DSDS simulations. Use when encoding correctness rules, post-run validation gates, compliance constraints, and safety checks that must hold across scenarios.