'post-mortem' 검색 결과

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnose problems before solving them: turn "X is broken and we don't know why" into a precise problem statement, verified root causes, solutions traced to those causes, and a rollout plan. Use whenever the user reports something failing, breaking, slowing, or recurring without a known cause: "sales dropped and we don't know why", "this keeps happening", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys"; Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng mà không rõ vì sao". Trigger even when the user asks for solutions directly: "give me ideas to fix falling sales" is a diagnosis request. Not for open-ended ideation when nothing is broken (brainstorm-coach), understanding user needs (design-thinking), or company-level strategic bets (strategy-board).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Monitor, cap, and recover from context accumulation in agentic systems. Covers per-cycle cost tracking, context window auditing, budget caps with enforcement policies, emergency pruning when approaching limits, and progressive disclosure integration to minimize token spend on routing. Use when running long-lived agent loops (heartbeats, polling, autonomous workflows), when context windows are growing unpredictably between cycles, when API costs spike beyond expected baselines, when designing new agentic workflows that need cost guardrails from the start, or when post-mortem analysis reveals a cost incident caused by context accumulation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or alert fatigue, improving incident response times, or after a post-mortem identifies handoff issues.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Tested output format specifications for Claude prompts. Use when the user wants a specific deliverable structure — retrieving, reviewing, customizing, or building output formatting. Trigger on: "give me the Executive Brief format," "show me the output template for," "I need the Decision Matrix structure," "show me available output formats," "build a custom output format for." Provides 10 ready-to-use structures (executive briefs, technical designs, research summaries, implementation plans, decision matrices, competitive analyses, post-mortems, stakeholder updates, strategic memos, process documentation) plus a custom template, with per-section length guidance and format constraints tested against Claude formatting defaults. If unsure which format fits, use rootnode-block-selection first if available. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or choosing reasoning/identity approaches (use rootnode-block-selection if available).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

INCIDENT MODE: Bypass standard PRD/Planning phase for emergency hotfixes. Requires immediate execution, a post-mortem ticket, and a patch release note.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Post-mortem analysis of a PhysicsIntern workspace run (Claude Code, Pi, Codex, or OpenCode host). Reconstructs the trajectory from the session record — JSONL file(s) for Claude/Pi/Codex, the SQLite store for OpenCode — audits methodology adherence against the workspace's own CLAUDE.md / AGENTS.md and skill/agent prompts, checks commit discipline and flag dispositions, and assesses substantive quality. Produces a thorough evidence-anchored markdown report. Use after a workspace has been worked on to identify what went well, where the methodology slipped, and what prompts to improve.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Capture learnings from a campaign, launch, sprint, or initiative using Five Whys (Taiichi Ohno, Toyota Production System) for root cause analysis and Start-Stop-Continue for action planning. Append reusable insights to knowledge/learnings.md so future runs of the OS get smarter. Use when the user asks for a retro, retrospective, post-mortem, "what did we learn", "campaign wrap-up", "lessons learned", or after a campaign or launch ends. Critical feedback loop that makes the OS compound over time. For the numbers review itself, see kpi-review. For planning the next campaign, see campaign-brief. For turning a sprint team's retro notes into action items, see retro-synthesizer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use during or right after an incident — frames severity, sets comms cadence, drafts the post-mortem skeleton — even when the user just says 'production is down' or 'wir haben einen Vorfall'.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use after an incident or outage is resolved — blame-free facilitation, root cause, corrective actions, memory write-back — even for a near-miss. Consumes the incident-commander skeleton.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Comprehensive incident response framework from detection through resolution and post-incident review. Battle-tested SRE/DevOps practices: severity classification, timeline reconstruction, structured post-incident analysis. Use when declaring an incident, coordinating multi-team response during an outage, leading a post-mortem, or setting up on-call practices for a new service.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product-discovery coach for Fishbowl engineers — inspired by Marty Cagan's work (never impersonates him). Stage-routes between opportunity brief, research, PRD, ticket drafting, and outcome review. Triggers on "product coach", "help me with product", "I need to write a PRD", "I want to do discovery", "opportunity assessment", "who is this for", "why are we building this", or when an engineer is starting, resuming, or post-mortem-ing product-adjacent work. Invoke with a short description of what you want to do, or invoke bare to be surveyed and routed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Send this coding session's transcript to the Convex team for an AI post-mortem that improves the quickstart system.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Send this coding session's transcript to the Convex team for an AI post-mortem that improves the quickstart system. Run only when the user explicitly asks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "run a launch retro / post-mortem", "compare launch results vs targets by channel", or "decide what to keep or kill for the next launch"; produces a structured D1/W1/M1 retrospective — a per-channel actual-vs-target table (UTM-attributed own analytics as the truth column, platform self-reported numbers as reference, every figure labeled Measured / User-provided / Estimated), a 5-Whys chain on the single largest miss, keep / kill / change decisions per channel, 3-5 actionable learnings for the next launch, and an outcome snapshot submitted to the launch registry. Not for return math (CPA / ROI) — use roi-calculator; not for the stakeholder-facing report writeup — use report-generator; not for a metric deep-dive — use performance-analyzer. 发布复盘/渠道归因/5-Whys/keep-kill

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps, post-mortem investigation with lldb/windbg/dotnet-dump analyze, profiling or tracing, or for .NET Framework processes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Send this coding session's transcript to the Convex team for an AI post-mortem that improves the quickstart system.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Debug Python: pdb REPL + debugpy remote (DAP).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management. Masters incident command, blameless post-mortems, error budget management, and system reliability patterns. Handles critical outages, communication strategies, and continuous improvement. Use IMMEDIATELY for production incidents or SRE practices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Complete observability & reliability engineering system. Use when designing monitoring, implementing structured logging, setting up distributed tracing, building alerting systems, creating SLO/SLI frameworks, running incident response, conducting post-mortems, or auditing system reliability. Covers all three pillars (logs/metrics/traces), alert design, dashboard architecture, on-call operations, chaos engineering, and cost optimization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.