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'.
日本語の概要は準備中です。原文の説明を表示しています。
lawve-ai/awesome-legal-skills☆ 8632026年10月3日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
minhnv0807/ai-business-skills☆ 6132026年9月12日 更新
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`.
日本語の概要は準備中です。原文の説明を表示しています。
minhnv0807/ai-business-skills☆ 6132026年9月12日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
HoangNguyen0403/agent-skills-standard☆ 5732026年10月12日 更新
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
日本語の概要は準備中です。原文の説明を表示しています。
bmad-code-org/bmad-module-game-dev-studio☆ 2512026年9月25日 更新
Post-interaction retrospective analysis — use after completing a significant task, conversation, or phase to extract lessons, identify process improvements, and update procedures
日本語の概要は準備中です。原文の説明を表示しています。
WingedGuardian/GENesis-AGI☆ 962026年10月13日 更新
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
日本語の概要は準備中です。原文の説明を表示しています。
striderZA/OpenCodeGameStudios☆ 932026年10月7日 更新
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
日本語の概要は準備中です。原文の説明を表示しています。
alibaba/opc-starter☆ 882026年7月22日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
cgallic/kai-cmo-harness☆ 562026年10月3日 更新
Structured retrospective after completing a delivery increment or diamond. Captures learning for continuous improvement.
日本語の概要は準備中です。原文の説明を表示しています。
haabe/mycelium☆ 462026年10月13日 更新
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".
日本語の概要は準備中です。原文の説明を表示しています。
WillNigri/Agentic-Tool-Optimization☆ 342026年9月8日 更新
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）。
ikeisuke/ai-dlc-starter-kit☆ 272026年7月26日 更新
Run a retro for personal global ~/.copilot assets and turn incident learnings into updates for copilot-instructions, instructions, skills, agents, and hooks. Not for workspace/repository assets, VS Code User Data assets, or a private skills repository. Triggers on retro, retrospective, incident learning, error analysis, copilot setup, instructions update, インシデント, and 知見反映.
aktsmm/Agent-Skills☆ 262026年10月13日 更新
"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.".
日本語の概要は準備中です。原文の説明を表示しています。
charlieviettq/awesome-agent-skill☆ 262026年7月20日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
hoavdc/CodexKit☆ 252026年10月11日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
hoavdc/CodexKit☆ 252026年10月11日 更新
Generates a sprint or milestone retrospective by analyzing completed work, velocity, blockers, and patterns. Produces actionable insights for the next iteration.
日本語の概要は準備中です。原文の説明を表示しています。
IdoCohen560/claude-unity-game-studio☆ 222026年7月8日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
tinh2/skills-hub-registry☆ 202026年9月5日 更新
Run a self-retrospective on a SKMTC-related session — generator authoring, CLI configuration, debugging, or any sustained interaction involving `@skmtc/core`, `@skmtc/cli`, or `@skmtc/gen-*` packages. Captures three distinct outputs: (1) friction entries (mistakes, surprises, overridden defaults, multi-cycle struggles), (2) a "knowledge acquired" block recording facts the agent learned during the session that weren't in its training — the primary signal for doc gaps — and (3) a closing priority list ranking the top 2-3 findings for docs/skills triage. Wins are logged only when they identify a pattern worth codifying that isn't already in a skill. Use this skill when the user asks to "retro", "skmtc retro", "log friction", "reflect on this session", "what did we learn", "run a retrospective", or after substantive SKMTC work (generator authoring, multi-step debugging, non-trivial CLI configuration) where capturing observations would help improve skills, docs, or SKMTC itself. Distinct from the `skmtc-cli` and `skmtc-generator` skills — those guide *doing* the work; this skill captures observations *about* the work. Do not invoke this skill during ordinary work; it is end-of- session (or mid-session-checkpoint) only.
日本語の概要は準備中です。原文の説明を表示しています。
skmtc/skmtc☆ 192026年10月12日 更新
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
日本語の概要は準備中です。原文の説明を表示しています。
youranreus/note☆ 122026年8月6日 更新
Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.
日本語の概要は準備中です。原文の説明を表示しています。
racecraft-lab/paddock-prototype☆ 122026年6月26日 更新
Summarises one sprint from the board export, sprint report and review or stand-up notes the user provides into a one-page DRAFT sprint review summary: the sprint goal as written, items delivered, items not delivered with the reasons the sources state, carry-over, impediments, metrics exactly as given, and numbered questions for the retrospective, every row referenced to a work item or note fragment and every missing fact marked UNKNOWN. Use when the user asks to "summarise the sprint", "write the sprint review", "what did we deliver this sprint", "list the carry-over and blockers" or "draft the sprint recap". Do not use for the retrospective write-up or themed lessons across several sprints, use lessons-learned-synthesis instead; for a weekly project status report, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
kesslernity/awesome-copilot-agent-skills☆ 82026年9月19日 更新
実際の作業結果からパターンを汎化し、次回に役立つ改善を提案する。振り返り・ふりかえり・retrospective・改善サイクル・エージェント定義の見直し・パターン分析に使う。`--meta` と `--dream` はユーザーが明示した場合の追加モード。ユーザーが /retro と入力したら使う。
coil398/dotfiles☆ 82026年10月13日 更新
運用で発見されたレビューパターン (findings / retrospective) を分析し、新 skill への昇格候補 / 既存 skill 更新候補 / 人間判断が必要な項目に分類する
s977043/river-review☆ 72026年10月13日 更新