跳到正文
cccskills
免费在 GitHub 公开

aar

After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.

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

查看安装方法

包含的文件(1)

  • SKILL.md2.4 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

After-Action Review

Conduct a structured debrief to extract learning from any significant event or experience.

Instructions

Work through the four core questions honestly and specifically. Focus on events and systems, not blaming individuals.

Output Format

Event: What are we reviewing? Date: When did it happen? Participants: Who was involved?


1. What Was Expected?

Before the event, what did we think would happen?

Goals/Objectives

  • [What were we trying to achieve?]

Plan

  • [What was the plan to achieve it?]

Success Criteria

  • [How would we know if we succeeded?]

Assumptions

  • [What did we assume would be true?]

2. What Actually Happened?

Facts only—what occurred, not why

Timeline

TimeEvent
[When][What happened]

Outcomes

  • [What results did we get?]

Compared to Expected

ExpectedActualGap
[expectation][reality][+/-]

3. Why the Difference?

Analysis of the gap between expected and actual

What Went Well (sustain these)

SuccessContributing Factors
[what worked][why it worked]

What Didn't Go Well (improve these)

ProblemRoot Cause
[what failed][why it failed]

Surprises

  • [Things we didn't anticipate]

4. What Do We Do Next?

Specific actions to sustain or improve

Sustain (keep doing these)

ActionOwnerHow to Protect It
[what to continue][who][mechanism]

Improve (change these)

ActionOwnerBy When
[what to change][who][deadline]

Key Takeaways Top 3 lessons from this review:

  1. [Lesson]
  2. [Lesson]
  3. [Lesson]

Follow-up When will we check if improvements are working?

Guidelines

  • Do this soon—memory fades fast
  • Be specific: "Communication failed" → "We didn't update Slack until hour 3"
  • Balance: Include what went well, not just problems
  • Assign owners: Insights without ownership become forgotten
  • Make it safe: Blame shuts down honesty

$ARGUMENTS

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.

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

MikeCheng1208/BattleTree22026年7月22日 更新

在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。

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

MikeCheng1208/BattleTree22026年7月22日 更新

Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.

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

MikeCheng1208/BattleTree22026年7月22日 更新

Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.

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

MikeCheng1208/BattleTree22026年7月22日 更新

Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.

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

MikeCheng1208/BattleTree22026年7月22日 更新

[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.

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

MikeCheng1208/BattleTree22026年7月22日 更新

查看 MikeCheng1208 的全部技能

报告此技能的问题