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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Conduct a structured debrief to extract learning from any significant event or experience.
Work through the four core questions honestly and specifically. Focus on events and systems, not blaming individuals.
Event: What are we reviewing? Date: When did it happen? Participants: Who was involved?
Before the event, what did we think would happen?
Goals/Objectives
Plan
Success Criteria
Assumptions
Facts only—what occurred, not why
Timeline
| Time | Event |
|---|---|
| [When] | [What happened] |
Outcomes
Compared to Expected
| Expected | Actual | Gap |
|---|---|---|
| [expectation] | [reality] | [+/-] |
Analysis of the gap between expected and actual
What Went Well (sustain these)
| Success | Contributing Factors |
|---|---|
| [what worked] | [why it worked] |
What Didn't Go Well (improve these)
| Problem | Root Cause |
|---|---|
| [what failed] | [why it failed] |
Surprises
Specific actions to sustain or improve
Sustain (keep doing these)
| Action | Owner | How to Protect It |
|---|---|---|
| [what to continue] | [who] | [mechanism] |
Improve (change these)
| Action | Owner | By When |
|---|---|---|
| [what to change] | [who] | [deadline] |
Key Takeaways Top 3 lessons from this review:
Follow-up When will we check if improvements are working?
$ARGUMENTS
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
在每次回复中使用固定前缀并列出本次实际参考的指令/文件，便于校验是否遵循上下文与规则。
The English summary is being prepared. Showing the original description.
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
The English summary is being prepared. Showing the original description.
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
[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.
The English summary is being prepared. Showing the original description.