176건 · 관련도순
Create slides for safety reviews, risk discussions, incident retrospectives, or security exercises. Warning stripes, three-level cards, status alerts, policy code blocks, checklists, and stacked bar charts provide a visual structure for the presentation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn supplied project evidence into Notion briefs, decision records, operational instructions, status updates, or retrospectives. Preserve existing page conventions and history, preview substantial changes, and verify the finished page with its title and link.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit whether prior learnings actually fired, then install mechanisms for this run's recurrences. No finding without an install path and a firing test. Triggers: retrospective, reflect, what did we learn, patterns, post-mortem, why does this keep happening.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compile a month-over-month retrospective from Agent Monitor data — sessions, cost, token volumes, completion rate, top projects by working directory, and notable shifts versus the prior month. Uses daily_sessions/daily_events (365d) from analytics, the session list, and the pricing cost breakdown. Use when doing a monthly retrospective or planning the month ahead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert agile coaching: framework selection, maturity assessment, retrospective facilitation, transformation roadmaps. Use when selecting an agile framework, coaching teams, facilitating retrospectives, or designing a transformation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sprint retrospective facilitation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture, structure, and recycle lessons from active and closed legal matters. Three modes: in-flight capture (triggered by scope changes, risk events, status updates — highest value), mid-matter review (phase gates or quarterly), and matter close retrospective (full structured findings). Lessons are formatted for immediate reuse, not filed and forgotten. Use when a risk materialises, a scope change lands, a phase completes, or a matter closes and you want to convert what happened into something useful for the next matter. Trigger on: 'capture a lesson', 'what did we learn', 'matter close', 'retrospective', 'lessons learned', 'what went wrong', 'what worked', 'phase gate review', 'debrief', 'extract the learning', 'close the matter', 'what should we do differently', 'pattern from this matter', 'improve the next one'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dung khi campaign DA KET THUC va can rut ra bai hoc dung cho lan sau — scorecard so lieu vs target, cai gi hieu qua, cai gi khong va vi sao co bang chung, bat ngo ngoai du doan, cap nhat playbook va Brand Hub, action item co nguoi chiu trach nhiem. Kich hoat khi user nhac 'retro campaign', 'retrospective', 'post-mortem', 'tong ket chien dich', 'bai hoc tu campaign', 'campaign vua roi rut ra gi', 'lan sau lam khac the nao'. Khong dung cho — bao cao so lieu dinh ky cho sep hoac khach thi dung skill 07-bao-cao-marketing; danh gia hieu suat tung nhan su thi dung skill 65-team-performance-review; ke hoach ads ky tiep thi dung skill 57-next-ads-plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs to WRITE a marketing report someone else will read — a one-page weekly for a CEO, a full monthly, or a quarterly strategy report with TL;DR, results versus target, insight, decisions needed, and next actions with owners. Trigger on 'marketing report', 'monthly report', 'weekly update for my boss', 'report for the client', 'quarterly summary', 'turn these numbers into a report'. Also use when the user says a stakeholder is asking how marketing is doing. Not for — diagnosing why the numbers are bad, see `03-performance-eval-global`; turning a raw export into insight, see `13-data-analysis-global`; a closed campaign retrospective, see `63-campaign-retrospective-global`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review session corrections, trigger misses and recurring agent mistakes to propose targeted skill-library changes. Use for retrospective, rework or routing-gap analysis before registry edits; load +common/common-learning-log for redacted evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Post-interaction retrospective analysis — use after completing a significant task, conversation, or phase to extract lessons, identify process improvements, and update procedures
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with trend tracking. Per-person breakdowns, shipping streaks, and actionable improvements. Use when asked for "retro", "weekly review", "what did we ship", or "engineering retrospective".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a learning retrospective on the Kai harness. Mines gate-failure logs and 30-day performance results into lessons, triages candidate lessons (promote/keep/retire), and graduates repeated lessons into enforced gate checks with golden corpus cases. Use when "retro", "what have we learned", "triage lessons", "promote lessons", "why does this keep failing", "harness retrospective", or monthly / after any heavy content sprint.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured retrospective after completing a delivery increment or diamond. Captures learning for continuous improvement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI-DLC v3（AI-Driven Development Lifecycle）のオーケストレーター。 define / develop / release / reflect の 4 フェーズコマンドと status / doctor の 補助コマンド、連続実行ラッパ express、旧名エイリアス（inception / construction / operations / retrospective）を統一的にルーティングする。 define / develop（normal / risky 含む）/ release / reflect の各フェーズフローと status / doctor の補助コマンドを実装済み（doctor は shallow scope）。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and facilitate structured workshops using Design Thinking and Liberating Structures. Produces detailed agendas with time blocks, facilitation notes, participant materials, and retrospective templates. Use when running ideation sessions, retrospectives, planning workshops, or collaborative problem-solving.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Facilitate and document Sprint Retrospectives per Scrum Guide 2020. Choose format by team maturity, structure the session, capture action items, and track improvement across sprints. Use after every sprint. Do not use for individual performance reviews, blame sessions, or annual assessments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a full retrospective and dev cycle analysis. Chains /recall → /new-features to reconstruct what went wrong, extract lessons learned, identify rework patterns, and synthesize feature ideas from the findings. Triggers: retrospective, retro, dev cycle analysis, what went wrong, lessons learned, postmortem, sprint retro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.